From 91755d380ff13b6657e62f86b279cfe5fdf9ee70 Mon Sep 17 00:00:00 2001
From: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>
Date: Wed, 8 Dec 2021 14:01:58 -0500
Subject: [PATCH] udpate to migrating page

---
 website/docs/cli/cloud/migrating.html.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/docs/cli/cloud/migrating.html.md b/website/docs/cli/cloud/migrating.html.md
index dc4a70ee5..5547b43b9 100644
--- a/website/docs/cli/cloud/migrating.html.md
+++ b/website/docs/cli/cloud/migrating.html.md
@@ -11,7 +11,7 @@ When you run `terraform init` in the following scenarios, Terraform will ask you
 
 1. [**Migrating from local state or state backends:**](#migrating-from-local-state-or-state-backends) If the working directory already has state data in one or more workspaces, Terraform will ask if you would like to migrate that state to new Terraform Cloud workspaces.
 
-2. [**Migrating from the `remote` backend:**](#migrating-from-the-remote-backend) If the working directory was already connected to Terraform Cloud with the `remote` backend, Terraform can continue using the same Terraform Cloud workspaces.
+2. [**Migrating from the `remote` backend:**](#migrating-from-the-remote-backend) If the working directory was already connected to Terraform Cloud with the `remote` backend, Terraform can continue using the same Terraform Cloud workspaces. You will need to switch the `remote` backend block to the `cloud` block.
 
 ## Migrating from Local State or State Backends
 
@@ -64,7 +64,7 @@ terraform {
  }
 ```
 
-#### Multiple workspaces
+#### Multiple Workspaces
 
 If you were using multiple workspaces with the `prefix` argument, replace it with a `cloud` block that uses the `tags` argument. You may specify any number of tags to distinguish the workspaces for your working directory, but a good starting point may be to use whatever the prefix was before.