Merge branch 'main' into main

Author: wadherv

docs/configuration.md

@@ -172,6 +172,7 @@ This module also allows you to run agents from a prebuilt AMI to gain faster sta
 ## AMI Configuration
 
 By default, the module will automatically select appropriate AMI images:
+
 - For Linux x64: Amazon Linux 2023 x86_64
 - For Linux ARM64: Amazon Linux 2023 ARM64
 - For Windows: Windows Server 2022 English Full ECS Optimized

docs/index.md

@@ -79,7 +79,7 @@ The Instance Termination Watcher is creating log and optional metrics for termin
 
     This feature is Beta, changes will not trigger a major release as long in beta.
 
-The Job Retry will allow you to retry scaling when a job is not started. When enabled the scale up lambda will send a retry message to the a SQS queue. The Job Retry lambda will check after a delay if the job is still queued, and if so, it will send a retry command to the scale up lambda via SQS. The feature is designed to be used with ephemeral runners. The feature is opt in, it will not be created by default.
+The Job Retry will allow you to retry scaling when a job is not started. When enabled the scale up lambda will send a retry message to the SQS queue. The Job Retry lambda will check after a delay if the job is still queued, and if so, it will send a retry command to the scale up lambda via SQS. The feature is designed to be used with ephemeral runners. The feature is opt in, it will not be created by default.
 
 Consequences of enabling the feature are:
 

examples/prebuilt/README.md

@@ -21,7 +21,7 @@ cd -
 
 ### Packer Image
 
-You will need to build your image. This example deployment uses the image example in `/images/linux-amz2`. You must build this image with packer in your AWS account first. Once you have built this you need to provider your owner ID as a variable
+You will need to build your image. This example deployment uses the image example in `/images/linux-amz2`. You must build this image with packer in your AWS account first. Once you have built this you need to provide your owner ID as a variable
 
 ## Deploy
 

modules/setup-iam-permissions/README.md

@@ -1,8 +1,8 @@
 # Module - IAM setup for using boundaries
 
-This module is optional and only added as example. You can deploy the root terraform module via you own IAM user with the right credentials. Alternatively you can create a role to deploy the root module with a limit boundary set.
+This module is optional and only added as example. You can deploy the root terraform module via your own IAM user with the right credentials. Alternatively you can create a role to deploy the root module with a limit boundary set.
 
-This module will create an AWS IAM role that is required to use permission boundaries. The created rol can be used to deploy the root module.
+This module will create an AWS IAM role that is required to use permission boundaries. The created role can be used to deploy the root module.
 
 ## Usages
 
@@ -33,7 +33,7 @@ output "boundary" {
 }
 ```
 
-Next execute the created Terraform code `terraform init && terraform apply` The module will. You can use the created role in your terraform provider with assume role and the boundary as well the namespace needs to be set to the root module.
+Next execute the created Terraform code via `terraform init && terraform apply`. You can use the created role in your terraform provider with assume role and the boundary as well the namespace needs to be set to the root module.
 
 
 <!-- BEGIN_TF_DOCS -->