From 0fc3d3d2f35520bb371c2dbca36d8e7a80501206 Mon Sep 17 00:00:00 2001 From: Toben Archer Date: Fri, 2 Sep 2022 16:21:39 -0500 Subject: [PATCH] Minor typo in example. (#1707) --- content/en/docs/instrumentation/js/api/tracing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/instrumentation/js/api/tracing.md b/content/en/docs/instrumentation/js/api/tracing.md index aa15027a1c91..66d4434177d5 100644 --- a/content/en/docs/instrumentation/js/api/tracing.md +++ b/content/en/docs/instrumentation/js/api/tracing.md @@ -71,7 +71,7 @@ server.on("GET", "/user/:id", onGet); Using span relationships, attributes, kind, and the related [semantic conventions]({{< relref "/docs/reference/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) {