From faffa11e08d0be227682d7dc3fd09472abce613a Mon Sep 17 00:00:00 2001
From: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>
Date: Wed, 9 Feb 2022 14:21:46 -0500
Subject: [PATCH] Update workspaces page

---
 website/docs/language/state/workspaces.mdx | 6 ++----
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/website/docs/language/state/workspaces.mdx b/website/docs/language/state/workspaces.mdx
index a3f38d447..ffd202074 100644
--- a/website/docs/language/state/workspaces.mdx
+++ b/website/docs/language/state/workspaces.mdx
@@ -201,8 +201,6 @@ The important thing about workspace internals is that workspaces are
 meant to be a shared resource. They aren't a private, local-only notion
 (unless you're using purely local state and not committing it).
 
-The "current workspace" name is stored only locally in the ignored
+The "current workspace" name is stored locally in the ignored
 `.terraform` directory. This allows multiple team members to work on
-different workspaces concurrently. The "current workspace" name is **not**
-currently meaningful in Terraform Cloud workspaces since it will always
-have the value `default`.
+different workspaces concurrently. Workspace names are also attached to associated remote workspaces in Terraform Cloud. For more details about workspace names in Terraform Cloud, refer to the [remote backend](/language/settings/backends/remote#workspaces) and [CLI Integration](/cli/cloud/settings#arguments) (recommended) documentation.