diff --git a/website/docs/language/settings/backends/index.html.md b/website/docs/language/settings/backends/index.html.md
index 21f573ab8..f0e9dca78 100644
--- a/website/docs/language/settings/backends/index.html.md
+++ b/website/docs/language/settings/backends/index.html.md
@@ -42,9 +42,9 @@ conflicts and inconsistencies.
 
 -> **Note:** In Terraform versions prior to 1.1.0, backends were also classified as being 'standard'
 or 'enhanced', where the latter term referred to the ability of the
-[remote](/docs/language/settings/sbackends/remote.html) backend to store state and perform
+[remote](/docs/language/settings/backends/remote.html) backend to store state and perform
 Terraform operations. This classification has been removed, clarifying the primary purpose of
-backends. Refer to [Configuring Terraform Cloud](/docs/language/settings/configuring-terraform-cloud) for details about how to
+backends. Refer to [Using Terraform Cloud ](/docs/cli/cloud/index.html) for details about how to
 store state, execute remote operations, and use Terraform Cloud directly from Terraform.
 
 ## Available Backends
diff --git a/website/docs/language/state/workspaces.html.md b/website/docs/language/state/workspaces.html.md
index c33cad7d3..8dcb7b5f4 100644
--- a/website/docs/language/state/workspaces.html.md
+++ b/website/docs/language/state/workspaces.html.md
@@ -46,8 +46,7 @@ organizations that use Terraform.
 different from but related to the Terraform Cloud
 [workspace](/docs/cloud/workspaces/index.html) concept.
 If you use multiple Terraform CLI workspaces in a single Terraform configuration
-and are migrating that configuration to Terraform Cloud, see this [migration
-document](/docs/cloud/migrate/workspaces.html).
+and are migrating that configuration to Terraform Cloud, refer to [Initializing and Migrating](/docs/cli/cloud/migrating.html).
 
 ## Using Workspaces