From 96b31fb1d351b472595f8b44fec8c45486d41bce Mon Sep 17 00:00:00 2001
From: Laura Pacilio <83350965+laurapacilio@users.noreply.github.com>
Date: Tue, 4 Jan 2022 15:43:52 -0500
Subject: [PATCH] Update core workflow page

---
 website/intro/core-workflow.mdx | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/website/intro/core-workflow.mdx b/website/intro/core-workflow.mdx
index 62afc53dc..6e44eb8d5 100644
--- a/website/intro/core-workflow.mdx
+++ b/website/intro/core-workflow.mdx
@@ -230,21 +230,22 @@ for a better experience at each step.
 Terraform Cloud provides a centralized and secure location for storing
 input variables and state while also bringing back a tight feedback loop for
 speculative plans for config authors. Terraform configuration interacts with
-Terraform Cloud via the ["remote" backend](/language/settings/backends/remote).
+Terraform Cloud via the [CLI integration](/cli/cloud).
 
 ```
 terraform {
-  backend "remote" {
+  cloud {
     organization = "my-org"
+    hostname = "app.terraform.io" # Optional; defaults to app.terraform.io
+
     workspaces {
-      prefix = "my-app-"
+      tags = ["networking", "source:cli"]
     }
   }
 }
 ```
 
-Once the backend is wired up, a Terraform Cloud API key is all that's
-needed by team members to be able to edit config and run speculative plans
+After you configure the integration, a Terraform Cloud API key is all your team members need to edit config and run speculative plans
 against the latest version of the state file using all the remotely stored
 input variables.