diff --git a/website/docs/language/settings/backends/s3.mdx b/website/docs/language/settings/backends/s3.mdx
index aed8ed20ff..9ed2a844e7 100644
--- a/website/docs/language/settings/backends/s3.mdx
+++ b/website/docs/language/settings/backends/s3.mdx
@@ -16,7 +16,7 @@ A single DynamoDB table can be used to lock multiple remote state files. Terrafo
 [Bucket Versioning](https://docs.aws.amazon.com/AmazonS3/latest/userguide/manage-versioning-examples.html)
 on the S3 bucket to allow for state recovery in the case of accidental deletions and human error.
 
--> **Note:** Becuase of the changes to the S3 Backend in Terraform 1.6, you may need to run `terraform init -reconfigure`,
+-> **Note:** Because of the changes to the S3 Backend in Terraform 1.6, you may need to run `terraform init -reconfigure`,
 even if there have been no changes to your backend configuration.
 
 ## Example Configuration
diff --git a/website/docs/language/upgrade-guides/index.mdx b/website/docs/language/upgrade-guides/index.mdx
index 924c946947..0e861a4915 100644
--- a/website/docs/language/upgrade-guides/index.mdx
+++ b/website/docs/language/upgrade-guides/index.mdx
@@ -139,7 +139,7 @@ The `run` block also applies or plans the main configuration by default, there i
 The S3 Backend has been updated, with a number of added and deprecated fields.
 These changes bring the S3 Backend configuration closer to the AWS Provider configuration.
 
--> **Note:** Becuase of these changes, you may need to run `terraform init -reconfigure`,
+-> **Note:** Because of these changes, you may need to run `terraform init -reconfigure`,
 even if there have been no changes to your backend configuration.
 
 ### Deprecations