diff --git a/_docs-sources/guides/stay-up-to-date/cis/cis-1.5.0/deployment-walkthrough/step-1-check-your-live-infrastructure-is-cis-v1.4-compliant.md b/_docs-sources/guides/stay-up-to-date/cis/cis-1.5.0/deployment-walkthrough/step-1-check-your-live-infrastructure-is-cis-v1.4-compliant.md index 2b48573a13..7d7e18fcb8 100644 --- a/_docs-sources/guides/stay-up-to-date/cis/cis-1.5.0/deployment-walkthrough/step-1-check-your-live-infrastructure-is-cis-v1.4-compliant.md +++ b/_docs-sources/guides/stay-up-to-date/cis/cis-1.5.0/deployment-walkthrough/step-1-check-your-live-infrastructure-is-cis-v1.4-compliant.md @@ -35,7 +35,7 @@ steampipe plugin install aws ## 1.2 Configure Steampipe to analyze all regions The file `~/.steampipe/config/aws.spc`, that is created by Steampipe, needs to be updated to analyze all regions, -by adding `regions = ["*"]`. Otherwise, multi-regions resouces, like AWS Config, IAM Access Analyzer will fail in the check: +by adding `regions = ["*"]`. Otherwise, multi-regions resources, like AWS Config, IAM Access Analyzer will fail in the check: ```hcl connection "aws" { diff --git a/docs/guides/stay-up-to-date/cis/cis-1.5.0/deployment-walkthrough/step-1-check-your-live-infrastructure-is-cis-v1.4-compliant.md b/docs/guides/stay-up-to-date/cis/cis-1.5.0/deployment-walkthrough/step-1-check-your-live-infrastructure-is-cis-v1.4-compliant.md index fb72b31b26..46d6714f44 100644 --- a/docs/guides/stay-up-to-date/cis/cis-1.5.0/deployment-walkthrough/step-1-check-your-live-infrastructure-is-cis-v1.4-compliant.md +++ b/docs/guides/stay-up-to-date/cis/cis-1.5.0/deployment-walkthrough/step-1-check-your-live-infrastructure-is-cis-v1.4-compliant.md @@ -35,7 +35,7 @@ steampipe plugin install aws ## 1.2 Configure Steampipe to analyze all regions The file `~/.steampipe/config/aws.spc`, that is created by Steampipe, needs to be updated to analyze all regions, -by adding `regions = ["*"]`. Otherwise, multi-regions resouces, like AWS Config, IAM Access Analyzer will fail in the check: +by adding `regions = ["*"]`. Otherwise, multi-regions resources, like AWS Config, IAM Access Analyzer will fail in the check: ```hcl connection "aws" { @@ -158,6 +158,6 @@ references to the Gruntwork Infrastructure as Code Library.