From 0fbee765d13e7f1cfc3d5529169a797b8dbd05a5 Mon Sep 17 00:00:00 2001 From: Martin Kuba Date: Thu, 31 Oct 2024 06:56:54 -0700 Subject: [PATCH] markdown lint --- plugins/node/opentelemetry-instrumentation-aws-lambda/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/node/opentelemetry-instrumentation-aws-lambda/README.md b/plugins/node/opentelemetry-instrumentation-aws-lambda/README.md index b95b7bf2ff..2adef75ff4 100644 --- a/plugins/node/opentelemetry-instrumentation-aws-lambda/README.md +++ b/plugins/node/opentelemetry-instrumentation-aws-lambda/README.md @@ -125,7 +125,7 @@ provider.register({ }); ``` -2. The OpenTelemetry SDK is configured to export traces to a backend other than AWX X-Ray, but the lambda function is invoked by other AWS services which send the context using the X-Ray HTTP headers. In this case, include the `AWSXRayPropagator`, which extracts context from the HTTP header but not the Lambda Active Tracing context. +1. The OpenTelemetry SDK is configured to export traces to a backend other than AWX X-Ray, but the lambda function is invoked by other AWS services which send the context using the X-Ray HTTP headers. In this case, include the `AWSXRayPropagator`, which extracts context from the HTTP header but not the Lambda Active Tracing context. ```js const { NodeTracerProvider } = require('@opentelemetry/sdk-trace-node');