fix typos

aquasecurity · Jun 27, 2024 · 8874dd7 · 8874dd7
1 parent 0d18e3b
commit 8874dd7
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/checks/aws/cloudtrail/enable-all-regions/index.md b/docs/checks/aws/cloudtrail/enable-all-regions/index.md
@@ -8,7 +8,7 @@ title: Cloudtrail should be enabled in all regions regardless of where your AWS
 
 ### Explanation
 
-When creating Cloudtrail in the AWS Management Console the trail is configured by default to be multi-region, this isn't the case with the Terraform resource. Cloudtrail should cover the full AWS account to ensure you can track changes in regions you are not actively operting in.
+When creating Cloudtrail in the AWS Management Console the trail is configured by default to be multi-region, this isn't the case with the Terraform resource. Cloudtrail should cover the full AWS account to ensure you can track changes in regions you are not actively operating in.
 
 ### Possible Impact
 Activity could be happening in your account in a different region

diff --git a/docs/checks/aws/redshift/use-vpc/index.md b/docs/checks/aws/redshift/use-vpc/index.md
@@ -8,7 +8,7 @@ title: Redshift cluster should be deployed into a specific VPC
 
 ### Explanation
 
-Redshift clusters that are created without subnet details will be created in EC2 classic mode, meaning that they will be outside of a known VPC and running in tennant.
+Redshift clusters that are created without subnet details will be created in EC2 classic mode, meaning that they will be outside of a known VPC and running in tenant.
 
 In order to benefit from the additional security features achieved with using an owned VPC, the subnet should be set.