tweak header

Author: rkoron007

website/data/cloud-docs-nav-data.json

@@ -393,7 +393,7 @@
         "title": "Publishing Private Modules",
         "path": "registry/publish-modules"
       },
-      { "title": "Manage Module Versions", "path": "registry/manage-module-versions" },
+      { "title": "Deprecate Module Versions", "path": "registry/manage-module-versions" },
       {
         "title": "Test-Integrated Modules",
         "path": "registry/test"

website/docs/cloud-docs/api-docs/private-registry/manage-module-versions.mdx

@@ -39,7 +39,9 @@ description: |-
 # Manage module version API
 Deprecating a module version in your organization’s private registry adds warnings to the module's registry page and warnings in the run outputs of any users of that version. 
 
-@import "partials/tfc-package-callouts/manage-module-version.mdx"
+<!-- BEGIN: TFC:only name:pnp-callout -->
+@include "tfc-package-callouts/manage-module-version.mdx"
+<!-- END: TFC:only name:pnp-callout -->
 
 Once you have deprecated a module version, you can revert its deprecation to remove the warnings from that version. For more details on module deprecation, refer to [Deprecate module versions](/terraform/cloud-docs/registry/deprecate-module-versions).
 

website/docs/cloud-docs/registry/manage-module-versions.mdx

@@ -7,14 +7,16 @@ description: >-
 # Deprecate module versions
 Deprecating a module version in your organization’s private registry adds warnings to the module's registry page and warnings in the run outputs of any users of that version. Once you have deprecated a module version, you can revert it back to remove the warnings from that version. 
 
-@import "partials/tfc-package-callouts/manage-module-version.mdx"
+<!-- BEGIN: TFC:only name:pnp-callout -->
+@include "tfc-package-callouts/manage-module-version.mdx"
+<!-- END: TFC:only name:pnp-callout -->
 
 Module deprecation is not available for users on legacy HCP Terraform team plans. Learn more about [migrating to current HCP Terraform plan](/terraform/cloud-docs/overview/migrate-teams-standard).
 
 ## Background
 Deprecating a module version allows platform teams and module authors to mark the end-of-life of specific private module versions. Deprecating a module version signifies to users that the version is temporarily maintained and available, but not recommended. 
 
-~> Note: The ability to deprecate module versions is in public beta. All APIs and workflows are subject to change.
+~> **Note**: The ability to deprecate module versions is in public beta. All APIs and workflows are subject to change.
 
 You can deprecate a private module version to warn existing users to upgrade that version in their configuration. The private registry also denotes which module versions are deprecated, alerting new consumers that they should use a non-deprecated version instead.