Fixing a small detail in the monorepo modules enablement (#829)

The option is within the organization's settings not in the workspace's
settings.

Author: trujillo-adam

content/terraform-docs-common/docs/cloud-docs/registry/publish-modules.mdx

@@ -58,7 +58,7 @@ For example, you could use the following release tags in your Git repository:
 
 Then, you could specify `app-` in the **Module Tag Prefix** field when configuring the settings for publishing modules in HCP Terraform or Terraform Enterprise. As a result, the platform selects the module tagged with `app-v1.0.0` and publishes `v1.0.0` to the registry. In this example, HCP Terraform or Terraform Enterprise would also publish version `v1.0.1` of the module when a new release in the repository is tagged with `app-v1.0.1`.   
 
-To change the default behavior, you can disable the **Publish modules to your private registry from a single repository** option in your workspace's general settings. When disabled, you should store the source code for each module in separate repositories, otherwise HCP Terraform and Terraform Enterprise may publish new versions of all modules in the repository each time you create a new release tag. 
+To change the default behavior, you can disable the **Publish modules to your private registry from a single repository** option in your organization settings. When disabled, you should store the source code for each module in separate repositories, otherwise HCP Terraform and Terraform Enterprise may publish new versions of all modules in the repository each time you create a new release tag. 
 
 ## Publish a new module