From 9452607a7f89d71dfdfad570a90eb11924b0187a Mon Sep 17 00:00:00 2001 From: matthew Date: Wed, 6 Sep 2023 18:13:53 +0900 Subject: [PATCH] docs(guidelines) tiny fix, add comma on docs (#4119) --- doc/tracing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/tracing.md b/doc/tracing.md index ea3e38284b..fb3371d4fa 100644 --- a/doc/tracing.md +++ b/doc/tracing.md @@ -79,7 +79,7 @@ server.on("GET", "/user/:id", onGet); Using span relationships, attributes, kind, and the related [semantic conventions](https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/trace/semantic_conventions), we can more accurately describe the span in a way our tracing backend will more easily understand. The following example uses these mechanisms, which are described below. ```typescript -import { NetTransportValues SemanticAttributes } from '@opentelemetry/semantic-conventions'; +import { NetTransportValues, SemanticAttributes } from '@opentelemetry/semantic-conventions'; import { trace, context, SpanKind, SpanStatusCode } from '@opentelemetry/api'; async function onGet(request, response) {