Merge branch 'mg_no_code_prov' of github.com:hashicorp/terraform-docs…

…-common-internal into mg_no_code_prov

website/docs/cloud-docs/no-code-provisioning/provisioning.mdx

@@ -7,7 +7,7 @@ description: How to provision infrastructure from a no-code ready module.
 
 -> **Note:** No-code provisioning is in beta and available in the [Terraform Cloud Business tier](https://www.hashicorp.com/products/terraform/pricing).
 
-No-code provisioning lets you deploy infrastructure resources in a new Terraform Cloud workspace without writing any Terraform configuration.
+No-code provisioning lets you deploy infrastructure resources in a new Terraform Cloud workspace without writing any Terraform configuration. You can create a no-code workspace from any module labeled **No-code Ready** in your organization's [private registry](/cloud-docs/registry).
 
 The no-code provisioning workflow is best for quickly deploying relatively static infrastructure. Beyond changing variable values, you cannot apply configuration changes to existing no-code workspaces. If you need to deploy updates to the no-code ready module's configuration, you must create new no-code workspaces with new resources. We recommend standard modules for use cases that require dynamic configuration and development.
 
@@ -19,7 +19,7 @@ To use no-code provisioning, you need permissions to [manage workspaces](/cloud-
 
 ## Provider Credentials
 
-Terraform automatically starts a new run to provision no-code infrastructure upon workspace creation. No-code modules contain provider blocks in their configuration, but still require provider credentials for successful deployment. Organization administrators determine [how new workspaces access provider credentials](/cloud-docs/no-code-provisioning/module-design#provider-credentials), which may require specific module design.
+Terraform automatically starts a new run to provision no-code infrastructure upon workspace creation. No-code modules contain provider blocks in their configuration, but still require provider credentials for successful deployment. Organization administrators determine how new workspaces should [access provider credentials](/cloud-docs/no-code-provisioning/module-design#provider-credentials), which may require specific module design.
 
 ## Creating a Workspace and Deploying Resources
 
@@ -35,7 +35,7 @@ To launch the no-code workflow:
 
      Terraform Cloud scans the module configuration for input variables and prompts for values for any variables without defaults or undefined in an existing global variable set. Terraform requires values for these variables to successfully complete runs in the workspace. Terraform Cloud performs type validation for the variable values if the module configuration specifies a type.
 
-1. Set values for the input variables. You can choose to skip this step and configure the variables later. However, Terraform Cloud does not prompt you for these values again and your Terraform runs may fail.
+1. (Optional) Set values for the input variables. You can choose to skip this step and configure the variables later. However, Terraform Cloud does not prompt you for these values again and your Terraform runs may fail.
 
 1. Cick **Next: Workspace settings**.
 
@@ -49,6 +49,6 @@ To launch the no-code workflow:
 
 ## Operations in No-Code Workspaces
 
-No-code workspaces have a limited feature set because you cannot access the resource configuration. However, you can edit workspace variables and settings, including notifications, permissions, and run triggers to connect the workspace to one or more source workspaces. They can also trigger new runs to pick up changes to variables, or queue destroy runs.
+No-code workspaces have a limited feature set because you cannot access the resource configuration. However, you can edit workspace variables and settings, including notifications, permissions, and run triggers. You can use run triggers to connect the workspace to one or more source workspaces, start new runs when you change workspace variables, or queue destroy runs.
 
 If the module’s configuration changes, you must destroy the workspace and create a new one to provision resources with the updated configuration.

website/docs/cloud-docs/registry/add.mdx

@@ -51,7 +51,7 @@ To add a public provider or module:
 
 You can enable no-code provisioning for public modules after adding them to your registry.
 
-To support the auto-apply workflow, ensure that downstream users can automatically load provider credentials into their new no-code workspaces. You can enable access by either creating a global variable set with the credentials for the module's provider, or by accessing outputs with credentials across workspaces. Refer to [Provider Credentials](/cloud-docs/no-code-provisioning/module-design#provider-credentials) for more details.
+To support the auto-apply workflow, ensure that downstream users can automatically load provider credentials into their new no-code workspaces. You can enable access by either creating a global variable set with the credentials for the module's provider, or by accessing outputs with credentials from other workspaces. Refer to [Provider Credentials](/cloud-docs/no-code-provisioning/module-design#provider-credentials) for more details.
 
 To enable no-code provisioning:
 1. Verify that the module meets the [requirements for no-code provisioning](/cloud-docs/no-code-provisioning/module-design#requirements).