AWS EC2 -> Amazon EC2 (#585)

Author: deki

src/docs/getting-started/go-sdk/manual-instr.mdx

@@ -123,7 +123,7 @@ otel.SetTextMapPropagator(xray.Propagator{})
 
 ### Using the AWS resource Detectors
 
-OpenTelemetry Go SDK has AWS EC2, ECS and EKS resource detector support. The resource detectors are responsible for detecting whether a Go application instrumented with OpenTelemetry is running on the respective environment, and populating resource attributes for that environment if available. If the resource detector detects that the application
+OpenTelemetry Go SDK has Amazon EC2, ECS and EKS resource detector support. The resource detectors are responsible for detecting whether a Go application instrumented with OpenTelemetry is running on the respective environment, and populating resource attributes for that environment if available. If the resource detector detects that the application
 is not running on an environment (EC2, ECS or EKS), then it will return an empty `resource` struct.
 
 <img src={goImg5} alt="Diagram" style="margin: 30px 0;" />

src/docs/getting-started/prometheus-remote-write-exporter/ecs.mdx

@@ -15,7 +15,7 @@ import availableMetricsECSImg from "assets/img/docs/gettingStarted/prometheus/ec
 In this guide, we'll enable Prometheus collection for an ECS cluster on EC2 and an ECS cluster on Fargate. In this scenario, we will use the Prometheus Receiver to scrape from
 applications and the AWS ECS Container Metrics Receiver to scrape infrastructure metrics. We will scrape from an application that provides us with some example Prometheus metrics.
 
-For ECS clusters powered by both AWS Fargate or AWS EC2, we will create a task definition of an ADOT Collector and a Prometheus metric emitter sample app. 
+For ECS clusters powered by both AWS Fargate or Amazon EC2, we will create a task definition of an ADOT Collector and a Prometheus metric emitter sample app.
 
 Our ADOT Collector configurations will contain two pipelines. 
 
@@ -130,7 +130,7 @@ Next, push this image to a remote repository on either ECR or Dockerhub so that
 
 <SectionSeparator />
 
-## Demonstration 2: ECS Powered by AWS EC2
+## Demonstration 2: ECS Powered by Amazon EC2
 
 Note that you must have a cluster created with an EC2 instance available. We chose “EC2 Linux + Networking” template. For more detailed cluster setup please refer to the link in the prerequisites section of this document.
 

src/docs/getting-started/python-sdk/manual-instr.mdx

@@ -124,7 +124,7 @@ When you install `opentelemetry-sdk-extension-aws`, you automatically get AWS Re
 
 The ADOT Python SDK supports automatically recording metadata in EC2, Elastic Beanstalk, ECS, and EKS environments.
 
-For example, if tracing with OpenTelemetry on an AWS EC2 instance, you can automatically populate `resource` attributes by creating a `TraceProvider` using the `AwsEc2ResourceDetector`:
+For example, if tracing with OpenTelemetry on an Amazon EC2 instance, you can automatically populate `resource` attributes by creating a `TraceProvider` using the `AwsEc2ResourceDetector`:
 
 
 ```python lineNumbers=true

src/docs/getting-started/ruby-sdk/trace-manual-instr.mdx

@@ -189,7 +189,7 @@ TODO: Update this section when ADOT Ruby Resource Detectors have been contribute
 
 The ADOT Ruby SDK supports automatically detecting and recording metadata from resources such as EC2, Elastic Beanstalk, ECS, and EKS.
 
-For example, if tracing with OpenTelemetry Ruby on an AWS EC2 instance, you can automatically populate `resource` attributes by initializing the OpenTelemetry Ruby SDK `TraceProvider` to use the `AwsEc2ResourceDetector`:
+For example, if tracing with OpenTelemetry Ruby on an Amazon EC2 instance, you can automatically populate `resource` attributes by initializing the OpenTelemetry Ruby SDK `TraceProvider` to use the `AwsEc2ResourceDetector`:
 
 ```ruby lineNumbers=true
 OpenTelemetry::SDK.configure do |c|

src/docs/setup/build-collector-as-debian.mdx

@@ -9,9 +9,9 @@ import SectionSeparator from "components/MdxSectionSeparator/sectionSeparator.js
 
 <SectionSeparator />
 
-## Run ADOTCollector Beta on AWS EC2 Debian(ubuntu)
+## Run ADOTCollector Beta on Amazon EC2 Debian(ubuntu)
 
-To run ADOTCollector on AWS EC2 debian host, you can choose to install ADOTCollector Debian on your host by the following steps.
+To run ADOTCollector on Amazon EC2 debian host, you can choose to install ADOTCollector Debian on your host by the following steps.
 
 **Steps,**
 

src/docs/setup/build-collector-as-rpm.mdx

@@ -9,9 +9,9 @@ import SectionSeparator from "components/MdxSectionSeparator/sectionSeparator.js
 
 <SectionSeparator />
 
-## Run ADOT Collector on AWS EC2 Linux
+## Run ADOT Collector on Amazon EC2 Linux
 
-To run ADOT Collector on AWS EC2 Linux host, you can choose to install ADOT Collector RPM on your host by the following steps.
+To run ADOT Collector on Amazon EC2 Linux host, you can choose to install ADOT Collector RPM on your host by the following steps.
 
 **Steps,**
 

src/docs/setup/ec2.mdx

@@ -64,7 +64,7 @@ aws cloudformation create-stack --stack-name AOCEC2-Test \
     --capabilities CAPABILITY_NAMED_IAM \
     --region ${Region}
 ```
-3. Go to AWS EC2 Console and verify there is a new EC2 instance that has been launched.
+3. Go to Amazon EC2 Console and verify there is a new EC2 instance that has been launched.
 4. Select the instance, and then choose *Connect. *You can login to the EC2 host with the example command below.
 ```
 ssh -i "<ec2-ssh-key-name>.pem" ec2-user@ec2-<instance_id>.us-west-2.compute.amazonaws.com (mailto:[email protected])