aws · mergify · May 13, 2021 · Apr 24, 2021 · May 13, 2021
diff --git a/packages/@aws-cdk/aws-appmesh/README.md b/packages/@aws-cdk/aws-appmesh/README.md
@@ -27,7 +27,7 @@ App Mesh gives you consistent visibility and network traffic controls for every
 
 App Mesh supports microservice applications that use service discovery naming for their components. To use App Mesh, you must have an existing application running on AWS Fargate, Amazon ECS, Amazon EKS, Kubernetes on AWS, or Amazon EC2.
 
-For futher information on **AWS AppMesh** visit the [AWS Docs for AppMesh](https://docs.aws.amazon.com/app-mesh/index.html).
+For further information on **AWS AppMesh** visit the [AWS Docs for AppMesh](https://docs.aws.amazon.com/app-mesh/index.html).
 
 ## Create the App and Stack
 

diff --git a/packages/@aws-cdk/aws-appsync/README.md b/packages/@aws-cdk/aws-appsync/README.md
@@ -759,7 +759,7 @@ You can create Object Types in three ways:
       name: 'demo',
     });
     const demo = new appsync.ObjectType('Demo', {
-      defintion: {
+      definition: {
         id: appsync.GraphqlType.string({ isRequired: true }),
         version: appsync.GraphqlType.string({ isRequired: true }),
       },
@@ -782,7 +782,7 @@ You can create Object Types in three ways:
     ```ts
     import { required_string } from './scalar-types';
     export const demo = new appsync.ObjectType('Demo', {
-      defintion: {
+      definition: {
         id: required_string,
         version: required_string,
       },
@@ -806,7 +806,7 @@ You can create Object Types in three ways:
     });
     const demo = new appsync.ObjectType('Demo', {
       interfaceTypes: [ node ],
-      defintion: {
+      definition: {
         version: appsync.GraphqlType.string({ isRequired: true }),
       },
     });

diff --git a/packages/@aws-cdk/aws-eks/README.md b/packages/@aws-cdk/aws-eks/README.md
@@ -654,7 +654,7 @@ const cluster = new eks.Cluster(this, 'MyCluster', {
 });
 ```
 
-You can also use a similiar configuration for running a cluster built using the FargateCluster construct.
+You can also use a similar configuration for running a cluster built using the FargateCluster construct.
 
 ```ts
 const secretsKey = new kms.Key(this, 'SecretsKey');

diff --git a/packages/@aws-cdk/aws-s3-deployment/README.md b/packages/@aws-cdk/aws-s3-deployment/README.md
@@ -77,7 +77,7 @@ Configuring this has a few implications you should be aware of:
 - **Destination Changes**
 
   When the destination bucket or prefix is changed, all files in the previous destination will **first** be
-  deleted and then uploaded to the new destination location. This could have availablity implications
+  deleted and then uploaded to the new destination location. This could have availability implications
   on your users.
 
 ### General Recommendations

diff --git a/packages/@aws-cdk/pipelines/README.md b/packages/@aws-cdk/pipelines/README.md
@@ -596,7 +596,7 @@ to create it in. If you are deploying your application to different environments
 also have to bootstrap those and be sure to add a *trust* relationship.
 
 > This library requires a newer version of the bootstrapping stack which has
-> been updated specifically to support cross-account continous delivery. In the future,
+> been updated specifically to support cross-account continuous delivery. In the future,
 > this new bootstrapping stack will become the default, but for now it is still
 > opt-in.
 >
-Original file line number
+Diff line change
@@ Expand Up / @@ -654,7 +654,7 @@ const cluster = new eks.Cluster(this, 'MyCluster', { @@
     });
     ```
-    You can also use a similiar configuration for running a cluster built using the FargateCluster construct.
+    You can also use a similar configuration for running a cluster built using the FargateCluster construct.
     ```ts
     const secretsKey = new kms.Key(this, 'SecretsKey');
@@ Expand Down @@