Fix name of AWS products starting with "Amazon ..."

Author: antoineco

docs/apis/index.md

@@ -11,5 +11,4 @@ Knative API is [documented at the project](https://knative.dev/docs/reference/ap
 ## TriggerMesh Targets API
 
 * [Triggermesh Targets](./private-targets.md).
-* [Triggermesh AWS EventBridge target](./awseventbridge-target.md).
-
+* [Triggermesh Amazon EventBridge target](./awseventbridge-target.md).

docs/apis/private-targets.md

@@ -56,7 +56,7 @@ Resource Types:
 <h3 id="targets.triggermesh.io/v1alpha1.AWSKinesisTarget">AWSKinesisTarget
 </h3>
 <p>
-<p>AWSKinesisTarget is the Schema for an AWS Kinesis Target.</p>
+<p>AWSKinesisTarget is the Schema for an Amazon Kinesis Target.</p>
 </p>
 <table>
 <thead>
@@ -321,7 +321,7 @@ AWSTargetStatus
 <h3 id="targets.triggermesh.io/v1alpha1.AWSS3Target">AWSS3Target
 </h3>
 <p>
-<p>AWSS3Target is the Schema for an AWS s3 Target.</p>
+<p>AWSS3Target is the Schema for an Amazon S3 Target.</p>
 </p>
 <table>
 <thead>
@@ -575,7 +575,7 @@ AWSTargetStatus
 <h3 id="targets.triggermesh.io/v1alpha1.AWSSQSTarget">AWSSQSTarget
 </h3>
 <p>
-<p>AWSSQSTarget is the Schema for an AWS SQS Target.</p>
+<p>AWSSQSTarget is the Schema for an Amazon SQS Target.</p>
 </p>
 <table>
 <thead>
@@ -2878,7 +2878,7 @@ When this property is true, only the CloudEvent data is included.</p>
 <a href="#targets.triggermesh.io/v1alpha1.AWSS3TargetStatus">AWSS3TargetStatus</a>)
 </p>
 <p>
-<p>AWSTargetStatus communicates the observed state of the various  AWS Targets (from the controller).</p>
+<p>AWSTargetStatus communicates the observed state of the various AWS Targets (from the controller).</p>
 </p>
 <table>
 <thead>

docs/sources/awscognitouserpool.md

@@ -1,22 +1,22 @@
-# Event source for AWS Cognito User Pools
+# Event source for Amazon Cognito User Pools
 
-This event source captures messages from an [AWS Cognito User Pool][cup-docs] whenever a specific action, such as the
+This event source captures messages from an [Amazon Cognito User Pool][cup-docs] whenever a specific action, such as the
 creation of a new user, happens in the user identity pool.
 
 ## Prerequisite(s)
 
-- AWS Cognito User Pool
+- Amazon Cognito User Pool
 - Amazon Resource Name (ARN)
 - API Credentials
 
-### AWS Cognito User Pool
+### Amazon Cognito User Pool
 
-If you don't already have an AWS Cognito User Pool, create one by following the instructions in the [Getting started
+If you don't already have an Amazon Cognito User Pool, create one by following the instructions in the [Getting started
 with User Pools][cup-getting-started] guide.
 
 ### Amazon Resource Name (ARN)
 
-A fully qualified ARN is required to uniquely identify the AWS Cognito User Pool.
+A fully qualified ARN is required to uniquely identify the Amazon Cognito User Pool.
 
 ![User Pool ARN](../images/awscognitouserpool-source/userpool-arn.png)
 
@@ -53,7 +53,7 @@ It is considered a [good practice][iam-bestpractices] to create dedicated users
 programmatically access AWS services. Permissions can be added or revoked granularly for a given IAM user by attaching
 [IAM Policies][iam-policies] to it.
 
-As an example, the following policy contains the permissions required by the TriggerMesh AWS Cognito User Pool event
+As an example, the following policy contains the permissions required by the TriggerMesh Amazon Cognito User Pool event
 source to list users in any user pool associated with the AWS account:
 
 ```json
@@ -75,14 +75,14 @@ source to list users in any user pool associated with the AWS account:
 
 ## Deploying an instance of the Source
 
-Open the Bridge creation screen and add a source of type `AWS Cognito User Pool`.
+Open the Bridge creation screen and add a source of type `Amazon Cognito User Pool`.
 
 ![Search Results](../images/awscognitouserpool-source/source-cognito-userpool.png)
 
 In the Source creation form, give a name to the event source and add the following information:
 
 - [**Secret**][accesskey]: Reference to a [TriggerMesh secret][tm-secret] containing an Access Key ID and a Secret
-  Access Key to communicate with the AWS SQS API, as described in the previous sections.
+  Access Key to communicate with the Amazon Cognito API, as described in the previous sections.
 - [**AWS ARN**][arn]: ARN of the User Pool, as described in the previous sections.
 
 ![Source form](../images/awscognitouserpool-source/source-cognito-userpool-form.png)
@@ -92,14 +92,14 @@ components to the Bridge, then submit it.
 
 ![Bridge overview](../images/awscognitouserpool-source/bridge-form-target.png)
 
-A ready status on the main _Bridges_ page indicates that the event source is ready to receive notifications from the AWS
-Cognito User Pool.
+A ready status on the main _Bridges_ page indicates that the event source is ready to receive notifications from the
+Amazon Cognito User Pool.
 
 ![Bridge status](../images/awscognitouserpool-source/bridge-status.png)
 
 ## Event Types
 
-The AWS Cognito UserPool event source emits events of the following type:
+The Amazon Cognito User Pool event source emits events of the following type:
 
 - `com.amazon.cognito-idp.sync_trigger`
 

docs/sources/awsdynamodb.md

@@ -1,6 +1,6 @@
-# Event Source for AWS DynamoDB
+# Event Source for Amazon DynamoDB
 
-This event source captures changes to items stored in an [AWS DynamoDB Table][ddb-docs] by reading the time-ordered
+This event source captures changes to items stored in an [Amazon DynamoDB Table][ddb-docs] by reading the time-ordered
 sequence of item-level modifications from a [DynamoDB Stream][ddb-streams].
 
 ## Prerequisite(s)
@@ -11,8 +11,8 @@ sequence of item-level modifications from a [DynamoDB Stream][ddb-streams].
 
 ### DynamoDB Table and Stream
 
-If you don't already have an AWS DynamoDB Table, create one by following the instructions at [Getting Started with
-DynamoDB][ddb-gettingstarted]. In order for change notifications to be consumed by the TriggerMesh AWS DynamoDB event
+If you don't already have an Amazon DynamoDB Table, create one by following the instructions at [Getting Started with
+DynamoDB][ddb-gettingstarted]. In order for change notifications to be consumed by the TriggerMesh Amazon DynamoDB event
 source, it is mandatory to enable a [Stream][ddb-streams] on the DynamoDB Table. To do so, follow the instructions at
 [Enabling a Stream][ddb-stream-enable]. You are free to select the _View type_ that is the most suitable for your own
 usage of the event source.
@@ -21,7 +21,7 @@ usage of the event source.
 
 ### Amazon Resource Name (ARN)
 
-A fully qualified ARN is required to uniquely identify the AWS DynamoDB Table.
+A fully qualified ARN is required to uniquely identify the Amazon DynamoDB Table.
 
 This ARN can be obtained directly from the _Overview_ tab after clicking the DynamoDB Table name in the list of existing
 tables. It typically has the following format:
@@ -58,7 +58,7 @@ It is considered a [good practice][iam-bestpractices] to create dedicated users
 programmatically access AWS services. Permissions can be added or revoked granularly for a given IAM user by attaching
 [IAM Policies][iam-policies] to it.
 
-As an example, the following policy contains only the permissions required by the TriggerMesh AWS DynamoDB event
+As an example, the following policy contains only the permissions required by the TriggerMesh Amazon DynamoDB event
 source to operate:
 
 ```json
@@ -83,31 +83,31 @@ source to operate:
 
 ## Deploying an Instance of the Source
 
-Open the Bridge creation screen and add a source of type `AWS DynamoDB`.
+Open the Bridge creation screen and add a source of type `Amazon DynamoDB`.
 
-![Adding an AWS DynamoDB source](../images/awsdynamodb-source/create-bridge-1.png)
+![Adding an Amazon DynamoDB source](../images/awsdynamodb-source/create-bridge-1.png)
 
 In the Source creation form, give a name to the event source and add the following information:
 
 - [**AWS ARN**][arn]: ARN of the DynamoDB Table, as described in the previous sections.
 - [**AWS Secret**][accesskey]: Reference to a [TriggerMesh secret][tm-secret] containing an Access Key ID and a Secret
-  Access Key to communicate with the AWS DynamoDB API, as described in the previous sections.
+  Access Key to communicate with the Amazon DynamoDB API, as described in the previous sections.
 
-![AWS DynamoDB source form](../images/awsdynamodb-source/create-bridge-2.png)
+![Amazon DynamoDB source form](../images/awsdynamodb-source/create-bridge-2.png)
 
 After clicking the `Save` button, you will be taken back to the Bridge editor. Proceed to adding the remaining
 components to the Bridge, then submit it.
 
 ![Bridge overview](../images/awsdynamodb-source/create-bridge-3.png)
 
-A ready status on the main _Bridges_ page indicates that the event source is ready to receive notifications from the AWS
-DynamoDB Stream.
+A ready status on the main _Bridges_ page indicates that the event source is ready to receive notifications from the
+Amazon DynamoDB Stream.
 
 ![Bridge status](../images/bridge-status-green.png)
 
 ## Event Types
 
-The AWS DynamoDB event source emits events of the following types:
+The Amazon DynamoDB event source emits events of the following types:
 
 - `com.amazon.dynamodb.insert`
 - `com.amazon.dynamodb.modify`

docs/sources/awskinesis.md

@@ -1,6 +1,6 @@
-# Event Source for AWS Kinesis
+# Event Source for Amazon Kinesis
 
-This event source acts as a consumer of an [AWS Kinesis Data Stream][kinesis-docs] and forwards all messages it reads
+This event source acts as a consumer of an [Amazon Kinesis Data Stream][kinesis-docs] and forwards all messages it reads
 after wrapping them in a [CloudEvent][ce] envelope.
 
 ## Prerequisite(s)
@@ -11,12 +11,12 @@ after wrapping them in a [CloudEvent][ce] envelope.
 
 ### Kinesis Data Stream
 
-If you don't already have an AWS Kinesis Data Stream, create one by following the instructions at [Creating and Updating
-Data Streams][kinesis-stream-create].
+If you don't already have an Amazon Kinesis Data Stream, create one by following the instructions at [Creating and
+Updating Data Streams][kinesis-stream-create].
 
 ### Amazon Resource Name (ARN)
 
-A fully qualified ARN is required to uniquely identify the AWS Kinesis Stream.
+A fully qualified ARN is required to uniquely identify the Amazon Kinesis Stream.
 
 This ARN can be obtained directly from the overview page of the Kinesis Stream. It typically has the following format:
 
@@ -52,8 +52,8 @@ It is considered a [good practice][iam-bestpractices] to create dedicated users
 programmatically access AWS services. Permissions can be added or revoked granularly for a given IAM user by attaching
 [IAM Policies][iam-policies] to it.
 
-As an example, the following policy contains only the permissions required by the TriggerMesh AWS Kinesis event source
-to operate:
+As an example, the following policy contains only the permissions required by the TriggerMesh Amazon Kinesis event
+source to operate:
 
 ```json
 {
@@ -76,31 +76,31 @@ to operate:
 
 ## Deploying an Instance of the Source
 
-Open the Bridge creation screen and add a source of type `AWS Kinesis`.
+Open the Bridge creation screen and add a source of type `Amazon Kinesis`.
 
-![Adding an AWS Kinesis source](../images/awskinesis-source/create-bridge-1.png)
+![Adding an Amazon Kinesis source](../images/awskinesis-source/create-bridge-1.png)
 
 In the Source creation form, give a name to the event source and add the following information:
 
 - [**AWS ARN**][arn]: ARN of the Kinesis Data Stream, as described in the previous sections.
 - [**AWS Secret**][accesskey]: Reference to a [TriggerMesh secret][tm-secret] containing an Access Key ID and a Secret
-  Access Key to communicate with the AWS Kinesis API, as described in the previous sections.
+  Access Key to communicate with the Amazon Kinesis API, as described in the previous sections.
 
-![AWS Kinesis source form](../images/awskinesis-source/create-bridge-2.png)
+![Amazon Kinesis source form](../images/awskinesis-source/create-bridge-2.png)
 
 After clicking the `Save` button, you will be taken back to the Bridge editor. Proceed to adding the remaining
 components to the Bridge, then submit it.
 
 ![Bridge overview](../images/awskinesis-source/create-bridge-3.png)
 
-A ready status on the main _Bridges_ page indicates that the event source is ready to forward messages from the AWS
+A ready status on the main _Bridges_ page indicates that the event source is ready to forward messages from the Amazon
 Kinesis Data Stream.
 
 ![Bridge status](../images/bridge-status-green.png)
 
 ## Event Types
 
-The AWS Kinesis event source emits events of the following types:
+The Amazon Kinesis event source emits events of the following types:
 
 - `com.amazon.kinesis.stream_record`
 

docs/sources/awss3.md

@@ -115,7 +115,7 @@ according to Amazon's documentation: [Configuring a bucket for notifications][s3
 
 ## Deploying an Instance of the Source
 
-Open the Bridge creation screen and add a source of type `AWS S3`.
+Open the Bridge creation screen and add a source of type `Amazon S3`.
 
 ![Adding an Amazon S3 source](../images/awss3-source/create-bridge-1.png)
 
@@ -129,7 +129,7 @@ In the Source creation form, give a name to the event source and add the followi
   this queue yourself as described in the previous sections.
 - [**Event types**][s3-events]: List of event types to subscribe to.
 
-![AWS S3 source form](../images/awss3-source/create-bridge-2.png)
+![Amazon S3 source form](../images/awss3-source/create-bridge-2.png)
 
 After clicking the `Save` button, you will be taken back to the Bridge editor. Proceed by adding the remaining
 components to the Bridge, then submit it.

docs/sources/awssns.md

@@ -1,6 +1,6 @@
-# Event Source for AWS SNS
+# Event Source for Amazon SNS
 
-This event source subscribes to messages from a [AWS SNS topic][sns-docs] and sends them as CloudEvents to an event
+This event source subscribes to messages from a [Amazon SNS topic][sns-docs] and sends them as CloudEvents to an event
 sink.
 
 ## Prerequisite(s)
@@ -11,12 +11,12 @@ sink.
 
 ### SNS Topic (standard)
 
-If you don't already have an AWS SNS standard topic, create one by following the instructions in the [Getting started
+If you don't already have an Amazon SNS standard topic, create one by following the instructions in the [Getting started
 with Amazon SNS][sns-getting-started] guide.
 
 ### Amazon Resource Name (ARN)
 
-A fully qualified ARN is required to uniquely identify the AWS SNS topic.
+A fully qualified ARN is required to uniquely identify the Amazon SNS topic.
 
 ![SNS topic](../images/awssns-source/sns-topic.png)
 
@@ -54,7 +54,7 @@ It is considered a [good practice][iam-bestpractices] to create dedicated users
 programmatically access AWS services. Permissions can be added or revoked granularly for a given IAM user by attaching
 [IAM Policies][iam-policies] to it.
 
-As an example, the following policy contains the permissions required by the TriggerMesh AWS SNS event source to read
+As an example, the following policy contains the permissions required by the TriggerMesh Amazon SNS event source to read
 and delete messages from any topic linked to the AWS account:
 
 ```json
@@ -85,33 +85,33 @@ and delete messages from any topic linked to the AWS account:
 
 ## Deploying an Instance of the Source
 
-Open the Bridge creation screen and add a source of type `AWS SNS`.
+Open the Bridge creation screen and add a source of type `Amazon SNS`.
 
-![Adding an AWS SNS source](../images/awssns-source/bridge-form-sns-source.png)
+![Adding an Amazon SNS source](../images/awssns-source/bridge-form-sns-source.png)
 
 In the Source creation form, give a name to the event source and add the following information:
 
 - [**Secret**][accesskey]: Reference to a [TriggerMesh secret][tm-secret] containing an Access Key ID and a Secret
-  Access Key to communicate with the AWS SNS API, as described in the previous sections.
+  Access Key to communicate with the Amazon SNS API, as described in the previous sections.
 - [**AWS ARN**][arn]: ARN of the SNS topic, as described in the previous sections.
 - [**DeliveryPolicy**][sns-delivery-policy]: Delivery policy to define how Amazon SNS retries the delivery of messages
   to HTTP/S endpoints.
 
-![AWS SNS source form](../images/awssns-source/bridge-form-sns-source-form.png)
+![Amazon SNS source form](../images/awssns-source/bridge-form-sns-source-form.png)
 
 After clicking the `Save` button, you will be taken back to the Bridge editor. Proceed to adding the remaining
 components to the Bridge, then submit it.
 
 ![Bridge overview](../images/awssns-source/bridge-form-target.png)
 
-A ready status on the main _Bridges_ page indicates that the event source is ready to receive messages from the AWS SNS
-topic.
+A ready status on the main _Bridges_ page indicates that the event source is ready to receive messages from the Amazon
+SNS topic.
 
 ![Bridge status](../images/awssns-source/bridge-deployed.png)
 
 ## Event Types
 
-The AWS SNS event source emits events of the following type:
+The Amazon SNS event source emits events of the following type:
 
 - `com.amazon.sns.notification`