Correct AOT usage in docs

Author: vasireddy99

src/docs/getting-started/cloudwatch-metrics.mdx

@@ -83,9 +83,9 @@ The available dimension roll-up options in EMF exporter,
 
 ```
 awsemf:
-    log_group_name: 'AOTLogGroup'
-    log_stream_name: 'AOTLogStream'
-    namespace: 'AOTMetricNS'
+    log_group_name: 'ADOTLogGroup'
+    log_stream_name: 'ADOTLogStream'
+    namespace: 'ADOTMetricNS'
     dimension_rollup_option: 1
 ```
 

src/docs/getting-started/js-sdk/metric-manual-instr.mdx

@@ -1,7 +1,7 @@
 ---
 title: 'Metrics on AWS Distro for OpenTelemetry JavaScript SDK'
 description:
-    Metrics auto instrumentation has not been supported in AOT/OpenTelemetry yet. We have to manually instrumenting code
+    Metrics auto instrumentation has not been supported in ADOT/OpenTelemetry yet. We have to manually instrumenting code
     in the application to generate application metrics. Here is an example with steps for modifying application code to
     create metrics with JavaScript SDK.
 path: '/docs/getting-started/js-sdk/metric-manual-instr'
@@ -11,7 +11,7 @@ import SectionSeparator from "components/MdxSectionSeparator/sectionSeparator.js
 import img2 from "assets/img/docs/img2.png"
 import { Link } from "gatsby"
 
-Metrics auto instrumentation has not been supported in AOT/OpenTelemetry yet. We have to manually instrumenting code in the application to generate application metrics. Here is an example with steps for modifying application code to create metrics with JavaScript SDK.
+Metrics auto instrumentation has not been supported in ADOT/OpenTelemetry yet. We have to manually instrumenting code in the application to generate application metrics. Here is an example with steps for modifying application code to create metrics with JavaScript SDK.
 
 OpenTelemetry JavaScript SDK has provided metrics API for metrics instrumentation in applications. You can follow the steps and sample code below to create OpenTelemetry Metrics and send it over to ADOT Collector.
 

src/docs/setup/ecs.mdx

@@ -38,8 +38,8 @@ Definition, and using AWS Management Console. Follow any of the following three
 The CloudFormation template will create all the necessary resources to get the Collector ready. This option is recommended for the beginners 
 who are new to ECS.
 
-- <Link to="/docs/setup/ecs/cfn-for-ecs-ec2">Deploy AOT for ECS on EC2</Link>
-- <Link to="/docs/setup/ecs/cfn-for-ecs-fargate">Deploy AOT for ECS on Fargate</Link> 
+- <Link to="/docs/setup/ecs/cfn-for-ecs-ec2">Deploy ADOT for ECS on EC2</Link>
+- <Link to="/docs/setup/ecs/cfn-for-ecs-fargate">Deploy ADOT for ECS on Fargate</Link>
 
 ### 2.2 Setup using ECS Task Definition
 
@@ -73,7 +73,7 @@ three options to setup the collector.
 The CloudFormation template will create all the necessary resources to get the Collector ready. This option is recommended for the beginners
 who are new to ECS.
 
-- <Link to="/docs/setup/ecs/cfn-for-ecs-ec2-instance">Deploy AOT for ECS EC2 instance metrics</Link>
+- <Link to="/docs/setup/ecs/cfn-for-ecs-ec2-instance">Deploy ADOT for ECS EC2 instance metrics</Link>
 
 ### 3.2 Setup using ECS Task Definition
 

src/docs/setup/ecs/create-task-definition-console.mdx

@@ -74,7 +74,7 @@ of AOC is passive, if your application doesn’t emit the data to the port (X-ra
    *  Collect Application Metrics & Traces and Container Resource Metrics
 
       In the container definition section for   Environment Command section add `--config=/etc/ecs/container-insights/otel-task-metrics-config.yaml`,
-      which is  already included as part of AOT collector, select the ECS default configuration for Container Insights experience.
+      which is  already included as part of ADOT collector, select the ECS default configuration for Container Insights experience.
       This will collect Application Metrics, Traces  and task-level Container Resource Metrics, and send them to Amazon CloudWatch Metrics
       and AWS X-Ray. This configuration file can collect metrics and traces from the OpenTelemetry SDKs (OTLP)
       , X-Ray traces from the X-Ray SDKs and StatsD metrics from your app.
@@ -103,7 +103,7 @@ of AOC is passive, if your application doesn’t emit the data to the port (X-ra
        <img src={task12} alt="Diagram" style="margin: 30px 0;" />
        2.  In Environment Section, add Environment variable: **AWS_XRAY_DAEMON_ADDRESS** with **aws-otel-collector:2000**
        <img src={task13} alt="Diagram" style="margin: 30px 0;" />
-       3.  In the NETWORK SETTINGS Links, put the container name aws-otel-collector you used in step 6 as AOT collector.
+       3.  In the NETWORK SETTINGS Links, put the container name aws-otel-collector you used in step 6 as ADOT collector.
        <img src={task14} alt="Diagram" style="margin: 30px 0;" />
        4.  Keep the rest information as default and click add.
        <img src={task15} alt="Diagram" style="margin: 30px 0;" />