diff --git a/website/docs/cli/commands/apply.html.md b/website/docs/cli/commands/apply.html.md
index 42e9c1b417..6b87bf6d95 100644
--- a/website/docs/cli/commands/apply.html.md
+++ b/website/docs/cli/commands/apply.html.md
@@ -86,7 +86,7 @@ plan to remove it in Terraform v0.15. If your workflow relies on overriding
 the root module directory, use
 [the `-chdir` global option](./#switching-working-directory-with-chdir)
 instead, which works across all commands and makes Terraform consistently look
-in the given directory for all files it would normaly read or write in the
+in the given directory for all files it would normally read or write in the
 current working directory.
 
 If your previous use of this legacy pattern was also relying on Terraform
diff --git a/website/docs/cli/commands/init.html.md b/website/docs/cli/commands/init.html.md
index c0c2f12b55..04278636ed 100644
--- a/website/docs/cli/commands/init.html.md
+++ b/website/docs/cli/commands/init.html.md
@@ -189,7 +189,7 @@ plan to remove it in Terraform v0.15. If your workflow relies on overriding
 the root module directory, use
 [the `-chdir` global option](./#switching-working-directory-with-chdir)
 instead, which works across all commands and makes Terraform consistently look
-in the given directory for all files it would normaly read or write in the
+in the given directory for all files it would normally read or write in the
 current working directory.
 
 If your previous use of this legacy pattern was also relying on Terraform
diff --git a/website/docs/cli/commands/plan.html.md b/website/docs/cli/commands/plan.html.md
index 5b7b012e87..b9f04e84b0 100644
--- a/website/docs/cli/commands/plan.html.md
+++ b/website/docs/cli/commands/plan.html.md
@@ -148,7 +148,7 @@ plan to remove it in Terraform v0.15. If your workflow relies on overriding
 the root module directory, use
 [the `-chdir` global option](./#switching-working-directory-with-chdir)
 instead, which works across all commands and makes Terraform consistently look
-in the given directory for all files it would normaly read or write in the
+in the given directory for all files it would normally read or write in the
 current working directory.
 
 If your previous use of this legacy pattern was also relying on Terraform