readme and descriptions updated

cloudposse · Jun 20, 2023 · 8cb0e96 · 8cb0e96
1 parent 68ffd46
commit 8cb0e96
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -75,7 +75,7 @@ After running this action, apply Terraform with the companion action, [github-ac
 This GitHub Action requires AWS access for two different purposes. This action will attempt to first run `terraform plan` against a given component and 
 then will use another role to save that given Terraform Plan to an S3 Bucket with metadata in a DynamoDB table. We recommend configuring 
 [OpenID Connect with AWS](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services) 
-to allow GitHub to assume roles in AWS, and then deploying both a Terraform Plan role and a Terraform State role. 
+to allow GitHub to assume roles in AWS and then deploying both a Terraform Plan role and a Terraform State role. 
 For Cloud Posse documentation on setting up GitHub OIDC, see our [`github-oidc-provider` component](https://docs.cloudposse.com/components/library/aws/github-oidc-provider/).
 
 In order to store Terraform State, we configure an S3 Bucket to store plan files and a DynamoDB table to track plan metadata. Both will need to be deployed before running

diff --git a/README.yaml b/README.yaml
@@ -47,7 +47,7 @@ usage: |-
   This GitHub Action requires AWS access for two different purposes. This action will attempt to first run `terraform plan` against a given component and 
   then will use another role to save that given Terraform Plan to an S3 Bucket with metadata in a DynamoDB table. We recommend configuring 
   [OpenID Connect with AWS](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-amazon-web-services) 
-  to allow GitHub to assume roles in AWS, and then deploying both a Terraform Plan role and a Terraform State role. 
+  to allow GitHub to assume roles in AWS and then deploying both a Terraform Plan role and a Terraform State role. 
   For Cloud Posse documentation on setting up GitHub OIDC, see our [`github-oidc-provider` component](https://docs.cloudposse.com/components/library/aws/github-oidc-provider/).
 
   In order to store Terraform State, we configure an S3 Bucket to store plan files and a DynamoDB table to track plan metadata. Both will need to be deployed before running