From 03aa18ac20be69b4ff4e66f563baf74f927c0e38 Mon Sep 17 00:00:00 2001
From: Siva Guruvareddiar <1725781+sguruvar@users.noreply.github.com>
Date: Mon, 11 Nov 2024 11:00:22 -0600
Subject: [PATCH] Update lambda-based-observability-adot.md

---
 .../guides/serverless/oss/lambda-based-observability-adot.md    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docusaurus/docs/guides/serverless/oss/lambda-based-observability-adot.md b/docusaurus/docs/guides/serverless/oss/lambda-based-observability-adot.md
index 63dc84817..8cbb3154c 100644
--- a/docusaurus/docs/guides/serverless/oss/lambda-based-observability-adot.md
+++ b/docusaurus/docs/guides/serverless/oss/lambda-based-observability-adot.md
@@ -18,7 +18,7 @@ In this section of the observability best practices guide, we will deep dive on
 
 [AWS Distro for OpenTelemetry (ADOT)](https://aws-otel.github.io/docs/introduction) is a secure, production-ready, AWS-supported distribution of the Cloud Native Computing Foundation (CNCF) [OpenTelemetry (OTel)](https://opentelemetry.io/) project. Using ADOT, you can instrument your applications just once and send correlated metrics and traces to multiple monitoring solutions.
 
-AWS's managed [OpenTelemetry Lambda Layer](https://aws-otel.github.io/docs/getting-started/lambda) utilizes [OpenTelemetry Lambda Layer](https://github.com/open-telemetry/opentelemetry-lambda)  to export telemetry data asynchronously from AWS Lambda. It provides plug-and-play user experience by wrapping an AWS Lambda function, and by packaging the OpenTelemetry runtime specific SDK, trimmed down version of ADOT collector together with an out-of-the-box configuration for auto-instrumenting AWS Lambda functions. ADOT Lambda Layer collector components, such as Receivers, Exporters, and Extensions support integration with Amazon CloudWatch, Amazon OpenSearch Service, Amazon Managed Service for Prometheus, AWS X-Ray, and others. Find the complete list [here](https://github.com/aws-observability/aws-otel-lambda). ADOT also supports integrations with [partner solutions](https://aws.amazon.com/otel/partners).
+AWS's managed [OpenTelemetry Lambda Layer](https://aws-otel.github.io/docs/getting-started/lambda) utilizes [OpenTelemetry Lambda Layer](https://github.com/open-telemetry/opentelemetry-lambda)  to export telemetry data. It provides plug-and-play user experience by wrapping an AWS Lambda function, and by packaging the OpenTelemetry runtime specific SDK, trimmed down version of ADOT collector together with an out-of-the-box configuration for auto-instrumenting AWS Lambda functions. ADOT Lambda Layer collector components, such as Receivers, Exporters, and Extensions support integration with Amazon CloudWatch, Amazon OpenSearch Service, Amazon Managed Service for Prometheus, AWS X-Ray, and others. Find the complete list [here](https://github.com/aws-observability/aws-otel-lambda). ADOT also supports integrations with [partner solutions](https://aws.amazon.com/otel/partners).
 
 ADOT Lambda Layer supports both auto-instrumentation (for Python, NodeJS, and Java) as well as custom instrumentation for any specific set of libraries and SDKs. With auto-instrumentation, by default, the Lambda Layer is configured to export traces to AWS X-Ray. For custom instrumentation, you will need to include the corresponding library instrumentation from the respective [OpenTelemetry runtime instrumentation repository](https://github.com/open-telemetry) and modify your code to initialize it in your function.