Fix typos (#1744)

Author: deining

content/en/references/internal-endpoints.md

@@ -36,4 +36,4 @@ $ curl -v --request POST --header "Content-Type: application/json"  --data '{"ac
 
 The API path for the AWS internal resources is `/_aws`.
 These endpoints offer LocalStack-specific features in addition to the ones offered by the AWS services.
-For instance, `/aws/sqs/messages` conveniently access all messages withing a SQS queue, without deleting them.
+For instance, `/aws/sqs/messages` conveniently access all messages within a SQS queue, without deleting them.

content/en/references/network-troubleshooting/images-src/assets/script.svg

@@ -156,7 +156,7 @@ Resources:
 
   InternetGateway:
     Type: AWS::EC2::InternetGateway
-  GatewayAttachement:
+  GatewayAttachment:
     Type: AWS::EC2::VPCGatewayAttachment
     Properties:
       VpcId: !Ref 'VPC'
@@ -167,7 +167,7 @@ Resources:
       VpcId: !Ref 'VPC'
   PublicRoute:
     Type: AWS::EC2::Route
-    DependsOn: GatewayAttachement
+    DependsOn: GatewayAttachment
     Properties:
       RouteTableId: !Ref 'PublicRouteTable'
       DestinationCidrBlock: '0.0.0.0/0'

content/en/tutorials/ecs-ecr-container-app/index.md

@@ -187,7 +187,7 @@ Run the following command to create the function:
 
 {{< callout "note">}}
 Before creating the lambda function, please double check under which architecture you have built your image.
-If your image is built as arm64, you need to specify the lambda architecture when deploying or set `LAMBDA_IGNORE_ARCHTIECTURE=1` when starting LocalStack.
+If your image is built as arm64, you need to specify the lambda architecture when deploying or set `LAMBDA_IGNORE_ARCHITECTURE=1` when starting LocalStack.
 More information can be found [in our documentation regarding ARM support.]({{< ref "arm64-support" >}})
 {{< /callout >}}
 

content/en/tutorials/lambda-ecr-container-images/index.md

@@ -541,7 +541,7 @@ $ awslocal kafka describe-cluster --cluster-arn "arn:aws:kafka:us-east-1:0000000
 }
 ```
 
-Once the `State` is `ACTIV`, the cluster is ready to be used.
+Once the `State` is `ACTIVE`, the cluster is ready to be used.
 Now it's time to create our Glue Schema Registry:
 
 ```bash

content/en/tutorials/schema-evolution-glue-msk/index.md

@@ -163,7 +163,7 @@ The Resource Browser supports CRD (Create, Read, Delete) operations on DMS resou
 
 * **Create Endpoint**: To create a new endpoint, click on the **Create Endpoint** button and fill in necessary details such as the Endpoint Identifier, Endpoint Type, and Engine Name.
 * **View Endpoint**: To see the details of an endpoint, click on its ARN.
-  You can further click **Connections** and test a conenction by specifying the Replication Instance ARN.
+  You can further click **Connections** and test a connection by specifying the Replication Instance ARN.
 * **Delete Endpoint**: To remove an endpoint, select it, navigate to **Actions**, and click **Remove Selected**.
 
 ### Replication Tasks

content/en/user-guide/aws/dms/index.md

@@ -502,7 +502,7 @@ Please refer to [Libvirt Wiki](https://wiki.libvirt.org/Failed_to_connect_to_the
 {{< /callout >}}
 
 The Libvirt VM manager currently does not have full support for persistence.
-Underlying virtual machines and volumes are not persisted, only their mock respresentations are.
+Underlying virtual machines and volumes are not persisted, only their mock representations are.
 
 ### AMIs
 

content/en/user-guide/aws/ec2/index.md

@@ -73,7 +73,7 @@ Run the following command to apply a policy to the file system created in the pr
 {{< command >}}
 $ awslocal efs put-file-system-policy \
     --file-system-id <FILE_SYSTEM_ID> \
-    --policy "{\"Version\":\"2012-10-17\",\"Id\":\"ExamplePolicy01\",\"Statement\":[{\"Sid\":\"ExampleSatement01\",\"Effect\":\"Allow\",\"Principal\":{\"AWS\":\"*\"},\"Action\":[\"elasticfilesystem:ClientMount\",\"elasticfilesystem:ClientWrite\"],\"Resource\":\"arn:aws:elasticfilesystem:us-east-1:000000000000:file-system/fs-34feac549e66b814\"}]}"
+    --policy "{\"Version\":\"2012-10-17\",\"Id\":\"ExamplePolicy01\",\"Statement\":[{\"Sid\":\"ExampleStatement01\",\"Effect\":\"Allow\",\"Principal\":{\"AWS\":\"*\"},\"Action\":[\"elasticfilesystem:ClientMount\",\"elasticfilesystem:ClientWrite\"],\"Resource\":\"arn:aws:elasticfilesystem:us-east-1:000000000000:file-system/fs-34feac549e66b814\"}]}"
 {{< /command >}}
 
 You can list the file system policies using the [`DescribeFileSystemPolicy`](https://docs.aws.amazon.com/efs/latest/ug/API_DescribeFileSystemPolicy.html) API.

content/en/user-guide/aws/efs/index.md

@@ -111,7 +111,7 @@ $ awslocal acm-pca issue-certificate \
 </disable-copy>
 {{< /command >}}
 
-The CA certificate is now created and its ARN is indicated by the `CertficiateArn` parameter.
+The CA certificate is now created and its ARN is indicated by the `CertificateArn` parameter.
 
 ### Import CA Certificate
 

content/en/user-guide/aws/pca/index.md

@@ -384,7 +384,7 @@ You can access the subscription tokens in JSON format through `GET /_aws/sns/sub
 
 <br>
 
-In this example, we will susbcribe to an external SNS integration not confirming the subscription, retrieve the subscription token and manually confirm it:
+In this example, we will subscribe to an external SNS integration not confirming the subscription, retrieve the subscription token and manually confirm it:
 
 Create an SNS topic, and create a subscription to a external HTTP SNS integration: