Apply suggestions from code review

Co-authored-by: Robin Norwood <rnorwood@hashicorp.com>

website/docs/cli/cloud/settings.mdx

@@ -12,7 +12,7 @@ This topic describes how to connect the Terraform CLI to HCP Terraform. Integrat
 
 ## Overview
 
-Connecting the Terraform CLI to HCP Terraform links the working directory that contains your Terraform configurations to one or more HCP Terraform workspaces. This allows team members with access to the worksapce to provision and manage infrastructure using HCP Terraform. Additionally, HCP Terraform manages state data so that you do not have to maintain remote state objects. Refer to the following topics for additional information:
+Connecting the Terraform CLI to HCP Terraform links the working directory that contains your Terraform configurations to one or more HCP Terraform workspaces. This allows team members with access to the workspace to provision and manage infrastructure using HCP Terraform. Additionally, HCP Terraform manages state data so that you do not have to maintain remote state objects. Refer to the following topics for additional information:
 
 - [State overview](/terraform/language/state) in the Terraform configuration language reference.
 - [Terraform State in HCP Terraform](/terraform/cloud-docs/workspaces/state) in the HCP Terraform documentation.
@@ -43,7 +43,7 @@ Specify the following settings in the `cloud` block:
 - `organization`:  Specifies the name of an HCP Terraform organization to connect to.
 - `workspaces.tags`: Specifies a list of single-value string tags. Terraform links the working directory to existing workspaces in the organization that have matching tags. If there are no existing workspaces with matching tags, the Terraform CLI prompts you to create a new workspace that inherits the tags you specify in this field when you initialize the configuration.
 - `workspaces.name`: You can specify the name of an existing workspace to associate with the Terraform configuration instead of using tags. If you configure the `name`, you cannot use the `tags` configuration.
-- `workspaces.project`: You can specify the name of an existing project to limit associating the configuration with workspaces in the specific project.
+- `workspaces.project`: You can specify the name of an existing project. Terraform associates the configuration with workspaces in the project that match the `name` or `tags`. 
 
 Refer to the [`cloud` block reference](/terraform/language/terraform#terraform-cloud) for details about configuring the `cloud` block.
 
@@ -94,7 +94,7 @@ As a result, Terraform prompts you to rename workspaces according to a pattern r
 
 In the `terraform` block or `terraform.tf` file, replace `backend "remote"` with `cloud`. Terraform will continue to use the same ste of HCP Terraform workspaces.
 
-The following example migrates the state data for a single workspace:
+The following example migrates the state data for a single workspace named `my-app-prod` to an HCP Terraform organization named `my-org`.
 
 ```hcl
 terraform {
@@ -110,7 +110,7 @@ terraform {
 }
 ```
 
-If the `terraform` block or `terraform.tf` file uses the `prefix` argument to connect to multiple workspaces, you can specify a list of single-value string tags in the `tags` argument instead. During `terraform plan` or `terraform apply` operations, Terraform associates the configuration with workspaces that match the specified tags.
+If the `terraform` block or `terraform.tf` file uses the `prefix` argument to connect to multiple workspaces, you can specify a list of single-value string tags in the `tags` argument instead of using the `name` argument. During `terraform plan` or `terraform apply` operations, Terraform associates the configuration with workspaces that match the specified tags.
 
 The following example replaces the `my-app-` prefix with the `app:mine` tag:
 
@@ -129,7 +129,7 @@ terraform {
 
 ```
 
-Note that because the `cloud` block does not support the `prefix` argument, you must refer to workspaces by their full name when using the Terraform CLI after migration. For example, instead of running the `terraform workspace select prod` command, you would run `terraform workspace select my-app-prod` instead.
+Note that because the `cloud` block does not support the `prefix` argument, after you migrate your workspaces to HCP Terraform, you must refer to them by their full name when you use the Terraform CLI. For example, instead of running the `terraform workspace select prod` command, you would run `terraform workspace select my-app-prod` instead.
 
 ## Exclude files
 

website/docs/language/terraform.mdx

@@ -43,7 +43,7 @@ Use Terraform version constraints in a collaborative environment to ensure that
 
 Terraform prints an error and exits without taking actions when you use a version of Terraform that does not meet the version constraints to run the configuration.
 
-Modules associated with a configuration may also specify version constraints. You must use a  Terraform version that satisfies all version constraints associated with the configuration, including constraints defined in modules, to perform operations. Refer to [Modules](/terraform/language/modules) for additional information about Terraform modules.
+Modules associated with a configuration may also specify version constraints. You must use a Terraform version that satisfies all version constraints associated with the configuration, including constraints defined in modules, to perform operations. Refer to [Modules](/terraform/language/modules) for additional information about Terraform modules.
 
 The `required_version` configuration applies only to the version of Terraform CLI and not versions of provider plugins. Refer to [Provider Requirements](/terraform/language/providers/requirements) for additional information.
 
@@ -72,7 +72,7 @@ You cannot configure a `backend` block when the configuration also contains a [`
 
 ### `terraform{}.cloud`
 
-Specifies a set of configurations that allow the Terraform configuration to connect to either HCP Terraform or a Terraform Enterprise installation.
+Specifies a set of attributes that allow the Terraform configuration to connect to either HCP Terraform or a Terraform Enterprise installation. HCP Terraform and Terraform Enterprise provide state storage, remote execution, and other benefits. Refer to the [HCP Terraform](/terraform/cloud-docs) and [Terraform Enterprise](/terraform/enterprise) documentation for additional information.
 
 You can only provide one `cloud` block per configuration.
 
@@ -95,7 +95,7 @@ Specifies metadata for matching workspaces in HCP Terraform. Terraform associate
 
 | Attribute | Description | Data type |
 | --- | --- | --- |
-| `tags` | Specifies a list of flat single-value tags. Terraform associates the configuration with workspace that have all matching flat single-value tags. New workspaces created from the working directory inherit the tags. This attribute does not support key-value tags. You cannot set this attribute and the `name` attribute in the same configuration.  | Array of strings |
+| `tags` | Specifies a list of flat single-value tags. Terraform associates the configuration with workspaces that have all matching flat single-value tags. New workspaces created from the working directory inherit the tags. This attribute does not support key-value tags. You cannot set this attribute and the `name` attribute in the same configuration.  | Array of strings |
 | `name` | Specifies an HCP Terraform workspace name to associate the Terraform configuration with. You can only use the working directory with the workspace named in the configuration. You cannot manage the workspace from the Terraform CLI. You cannot set this attribute and the `tags` attribute in the same configuration. <p>Instead of hardcoding a single workspace as a string, you can alternatively use the [`TF_WORKSPACE`](#tf_workspace) environment variable. </p> | String |
 | `project` | Specifies the name of an HCP Terraform project. Terraform creates all workspaces that use this configuration in the project. Using the [`terraform workspace list` command](/terraform/cli/commands/workspace/list) in the working directory returns only workspaces in the specified project. <p>Instead of hardcoding the project as a string, you can alternatively use the [`TF_CLOUD_PROJECT`](#tf_cloud_project) environment variable.</p>| String |
 
@@ -202,7 +202,7 @@ terraform {
 
 ### Connect to Terraform Enterprise using environment variables
 
-In the following example, local values stored in the `TF_CLOUD_ORGANIZATION` and `TF_CLOUD_HOSTNAME` environment variables automatically populate the configuration. During initialization, the local Terraform CLI connects the working directory to Terraform Enterprise using local values that would otherwise be hard-coded using the `organization` and `hostname` arguments. This allows the configuration to link to ephemeral hostnames and allows teams to  reuse the configuration in different continuous integration pipelines:
+In the following example, Terraform checks the `TF_CLOUD_ORGANIZATION` and `TF_CLOUD_HOSTNAME` environment variables and automatically populates the `organization` and `hostname` arguments. During initialization, the local Terraform CLI connects the working directory to Terraform Enterprise using those values. As a result, Terraform links the configuration to either HCP Terraform or Terraform Enterprise and allows teams to  reuse the configuration in different continuous integration pipelines:
 
 ```hcl
 terraform {