diff --git a/website/docs/language/state/remote-state-data.mdx b/website/docs/language/state/remote-state-data.mdx
index 997d06e2d..a9c6bf93e 100644
--- a/website/docs/language/state/remote-state-data.mdx
+++ b/website/docs/language/state/remote-state-data.mdx
@@ -9,13 +9,12 @@ description: >-
 
 [backends]: /language/settings/backends
 
-The `terraform_remote_state` data source retrieves the root module output values
-from some other Terraform configuration, using the latest state snapshot from
-the remote backend.
+The `terraform_remote_state` data source uses the latest state snapshot from the remote backend to retrieve the root module output values
+from some other Terraform configuration.
 
-This data source implemented by a built-in provider with the [source address](/language/providers/requirements#source-addresses) `terraform.io/builtin/terraform`. That provider does not include any other resources or data sources. Because of this, the `terraform_remote_state` data source is always available; you do not need to require or configure a provider to use it.
+You can use the `terraform_remote_state` data source without requiring or configuring a provider. It is always available because it is implemented through a built-in provider with the [source address](/language/providers/requirements#source-addresses) `terraform.io/builtin/terraform`. That provider does not include any other resources or data sources.
 
--> **Warning:** To access remote state outputs in Terraform Cloud or Terraform Enterprise, we recommend using the [`tfe_outputs` data source](https://registry.terraform.io/providers/hashicorp/tfe/latest/docs/data-sources/outputs) in the [Terraform Cloud/Enterprise Provider](https://registry.terraform.io/providers/hashicorp/tfe/latest/docs). The `tfe_outputs` method is more secure because it does not require full access to state of a workspace to fetch the outputs. If you are using the [Terraform Cloud CLI integration](/docs/cli/cloud), you **must** use `tfe_outputs` because the integration is incompatible with `terraform_remote_state`.
+!> **Warning:** We recommend using the [`tfe_outputs` data source](https://registry.terraform.io/providers/hashicorp/tfe/latest/docs/data-sources/outputs) in the [Terraform Cloud/Enterprise Provider](https://registry.terraform.io/providers/hashicorp/tfe/latest/docs) to access remote state outputs in Terraform Cloud or Terraform Enterprise. The `tfe_outputs` data source is more secure because it does not require full access to workspace state to fetch outputs. If you are using the [Terraform Cloud CLI integration](/docs/cli/cloud), you **must** use `tfe_outputs` because the integration is incompatible with `terraform_remote_state`.
 
 ## Alternative Ways to Share Data Between Configurations
 
diff --git a/website/intro/core-workflow.mdx b/website/intro/core-workflow.mdx
index 6e44eb8d5..e73cb326d 100644
--- a/website/intro/core-workflow.mdx
+++ b/website/intro/core-workflow.mdx
@@ -229,8 +229,8 @@ 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 [CLI integration](/cli/cloud).
+speculative plans for config authors. Terraform configuration can interact with
+Terraform Cloud through the [CLI integration](/cli/cloud).
 
 ```
 terraform {