chore(deps): Fix goreleaser to use pinned version (#2148)

* chore(deps): Fix goreleaser to use pinned version

* fix typos

Author: simar7

Diff for: .github/workflows/gh_release.yml

@@ -42,7 +42,7 @@ jobs:
       - name: Release
         uses: goreleaser/goreleaser-action@v4
         with:
-          version: latest
-          args: release --rm-dist -f .goreleaser_github.yml
+          version: v1.25.1
+          args: release --clean -f .goreleaser_github.yml
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Diff for: .github/workflows/release.yml

@@ -41,8 +41,8 @@ jobs:
       - name: Release
         uses: goreleaser/goreleaser-action@v4
         with:
-          version: latest
-          args: release --rm-dist
+          version: v1.25.1
+          args: release --clean
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           SLACK_WEBHOOK: ${{ secrets.SLACK_WEBHOOK }}

Diff for: 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 for: 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.