Optimize (CQA) - Managing Content - RH Subs

guides/common/assembly_managing-red-hat-subscriptions.adoc

@@ -20,4 +20,4 @@ include::modules/proc_removing-red-hat-subscriptions-and-subscription-manifests.
 
 include::modules/proc_updating-and-refreshing-red-hat-subscription-manifests.adoc[leveloffset=+1]
 
-include::modules/con_content-delivery-network-structure.adoc[leveloffset=+1]
+include::modules/ref_red-hat-cdn-structure.adoc[leveloffset=+1]

guides/common/modules/con_importing-a-subscription-manifest-into-foreman-server.adoc

@@ -4,7 +4,8 @@
 = Importing a Red{nbsp}Hat subscription manifest into {ProjectServer}
 
 [role="_abstract"]
-Import a Red{nbsp}Hat subscription manifest into {ProjectServer} so that you can enable and synchronize Red{nbsp}Hat repositories.
+You can import a Red{nbsp}Hat subscription manifest into {ProjectServer} to provide subscription allocation to your organization in {Project}.
+You obtain the subscription manifest from a Red{nbsp}Hat self-service site.
 
 [NOTE]
 ====

guides/common/modules/con_managing-red-hat-subscriptions.adoc

@@ -4,12 +4,14 @@
 = Managing Red Hat subscriptions
 
 [role="_abstract"]
-{ProjectName} can import content from the Red{nbsp}Hat Content Delivery Network (CDN).
-{Project} requires a Red{nbsp}Hat subscription manifest to find, access, and download content from the corresponding repositories.
-You must have a Red{nbsp}Hat subscription manifest containing a subscription allocation for each organization on {ProjectServer}.
-All subscription information is available on the {RHCloud}.
+You can import content from the Red{nbsp}Hat Content Delivery Network (CDN) into {ProjectName} by using a Red{nbsp}Hat subscription manifest.
+Manage your subscription allocations to ensure each organization can access and download Red{nbsp}Hat repositories.
+
+A Red{nbsp}Hat subscription manifest contains the information about the subscriptions purchased from Red{nbsp}Hat.
+{Project} uses the information in the manifest to access the Red{nbsp}Hat CDN and find what repositories are available for the associated subscription.
 
-Use this chapter to import a Red{nbsp}Hat subscription manifest and manage the manifest within the {ProjectWebUI}.
+You must have a Red{nbsp}Hat subscription manifest containing a subscription allocation for each organization in {Project}.
+All subscription information is available on the {RHCloud}.
 
 Subscription allocations and organizations::
 You can manage more than one organization if you have more than one subscription allocation.

guides/common/modules/proc_adding-red-hat-subscriptions-to-subscription-manifests.adoc

@@ -4,15 +4,18 @@
 = Adding Red Hat subscriptions to subscription manifests
 
 [role="_abstract"]
-Use the following procedure to add Red Hat subscriptions to a subscription manifest in the {ProjectWebUI}.
+You can add Red{nbsp}Hat subscriptions to your subscription manifest to allocate entitlements to Red{nbsp}Hat content in your organization.
+
+If you have exported a new subscription manifest from the {RHCloud}, you have to populate the manifest with subscriptions.
+Such a manifest does not initially contain any subscriptions.
 
 .Prerequisites
-* You must have a Red{nbsp}Hat subscription manifest file imported to {ProjectServer}.
+* A Red{nbsp}Hat subscription manifest is imported to {ProjectServer}.
 For more information, see xref:Importing_a_Red_Hat_Subscription_Manifest_into_Server_{context}[].
 
 .Procedure
 . In the {ProjectWebUI}, ensure the context is set to the organization you want to use.
 . In the {ProjectWebUI}, navigate to *Content* > *Subscriptions*.
 . In the Subscriptions window, click *Add Subscriptions*.
 . On the row of each subscription you want to add, enter the quantity in the *Quantity to Allocate* column.
-. Click *Submit*
+. Click *Submit*.

guides/common/modules/proc_importing-red-hat-subscription-manifest-by-using-cli.adoc

@@ -5,10 +5,11 @@
 
 [role="_abstract"]
 You can import a Red{nbsp}Hat subscription manifest into {ProjectServer} by using Hammer CLI.
+Import the manifest so that you can enable and synchronize Red{nbsp}Hat repositories in your organization.
 
 .Prerequisites
-* You must have a Red{nbsp}Hat subscription manifest file.
-For more information, see xref:Importing_a_Red_Hat_Subscription_Manifest_into_Server_{context}[].
+* You have a Red{nbsp}Hat subscription manifest file.
+For more information, see xref:obtaining-a-red-hat-subscription-manifest[].
 
 .Procedure
 . Copy the Red{nbsp}Hat subscription manifest file from your local machine to {ProjectServer}:

guides/common/modules/proc_importing-red-hat-subscription-manifest-by-using-web-ui.adoc

@@ -5,10 +5,11 @@
 
 [role="_abstract"]
 You can import a Red{nbsp}Hat subscription manifest into {ProjectServer} by using {ProjectWebUI}.
+Import the manifest so that you can enable and synchronize Red{nbsp}Hat repositories in your organization.
 
 .Prerequisites
-* You must have a Red{nbsp}Hat subscription manifest file.
-For more information, see xref:Importing_a_Red_Hat_Subscription_Manifest_into_Server_{context}[].
+* You have a Red{nbsp}Hat subscription manifest file.
+For more information, see xref:obtaining-a-red-hat-subscription-manifest[].
 
 .Procedure
 . In the {ProjectWebUI}, ensure the context is set to the organization you want to use.

guides/common/modules/proc_locating-a-red-hat-subscription.adoc

@@ -4,11 +4,10 @@
 = Locating a Red Hat subscription
 
 [role="_abstract"]
-When you import a Red{nbsp}Hat subscription manifest into {ProjectServer}, the subscriptions from your manifest are listed in the Subscriptions window.
-If you have a high volume of subscriptions, you can filter the results to find a specific subscription.
+You can locate specific Red{nbsp}Hat subscriptions in your {ProjectServer} by filtering the results on the Subscriptions page to navigate a high volume of subscriptions.
 
 .Prerequisites
-* You must have a Red{nbsp}Hat subscription manifest file imported to {ProjectServer}.
+* A Red{nbsp}Hat subscription manifest is imported to {ProjectServer}.
 For more information, see xref:Importing_a_Red_Hat_Subscription_Manifest_into_Server_{context}[].
 
 .Procedure

guides/common/modules/proc_obtaining-a-red-hat-subscription-manifest.adoc

@@ -4,7 +4,10 @@
 = Obtaining a Red{nbsp}Hat subscription manifest
 
 [role="_abstract"]
-You need to create and export a Red{nbsp}Hat subscription manifest before you can import it into your {ProjectServer}.
+You can create and export a Red{nbsp}Hat subscription manifest to prepare subscriptions for import into {Project}.
+
+.Prerequisites
+* Your Red{nbsp}Hat account has permission to create and export a subscription manifest for use with {ProjectServer}.
 
 .Procedure
 ifeval::["{mode}" == "connected"]
@@ -25,11 +28,16 @@ ifdef::content-management[]
 ifndef::orcharhino[]
 For more information, see {RHDocsBaseURL}subscription_central/1-latest/html-single/creating_and_managing_manifests_for_a_connected_satellite_server/index[Creating and managing manifests for a connected Satellite Server] in _Subscription Central_.
 endif::[]
++
+This manifest does not yet contain any subscriptions.
+After you import the manifest into {Project}, add subscriptions to the manifest in {Project}.
 * If your {Project} is disconnected, use the Red{nbsp}Hat Customer Portal to create and export the manifest.
 ifndef::orcharhino[]
 For more information, see {RHDocsBaseURL}subscription_central/1-latest/html-single/creating_and_managing_manifests_for_a_disconnected_satellite_server/index[Creating and managing manifests for a disconnected Satellite Server] in _Subscription Central_.
 endif::[]
 endif::[]
++
+This manifest already contains subscriptions.
 ifeval::["{mode}" == "disconnected"]
 . Disable subscription connection on your {ProjectServer}.
 For more information, see xref:disabling-subscription-connection-by-using-web-ui[].

guides/common/modules/proc_removing-red-hat-subscriptions-and-subscription-manifests.adoc

@@ -4,7 +4,7 @@
 = Removing Red Hat subscriptions from subscription manifests
 
 [role="_abstract"]
-Use the following procedure to remove Red Hat subscriptions from a subscription manifest in the {ProjectWebUI}.
+You can remove Red{nbsp}Hat subscriptions from manifests to adjust entitlement allocations or decommission Red{nbsp}Hat products from your organization.
 
 [WARNING]
 ====
@@ -13,7 +13,7 @@ If you delete the manifest from the Red Hat Customer Portal or in the {ProjectWe
 ====
 
 .Prerequisites
-* You must have a Red{nbsp}Hat subscription manifest file imported to {ProjectServer}.
+* A Red{nbsp}Hat subscription manifest is imported to {ProjectServer}.
 For more information, see xref:Importing_a_Red_Hat_Subscription_Manifest_into_Server_{context}[].
 
 .Procedure

guides/common/modules/proc_tracking-subscription-usage-by-using-the-subscriptions-service.adoc

@@ -4,12 +4,14 @@
 = Tracking subscription usage by using the Subscriptions service
 
 [role="_abstract"]
-You can configure your {ProjectServer} to report usage data to the {RHCloud} by using the `foreman_rh_cloud` plugin.
+You can configure your {ProjectServer} to report usage data to the {RHCloud}.
+Track and manage your subscription usage to analyze historical trends for planning and compliance.
 
 ifndef::satellite[]
 .Prerequisites
-* Enable the `foreman_rh_cloud` plugin:
-+
+* The `foreman_rh_cloud` plugin is enabled on {ProjectServer}.
+If the plugin is not enabled, run the following command:
+
 [options="nowrap", subs="+quotes,verbatim,attributes"]
 ----
 # {foreman-installer} --enable-foreman-plugin-rh-cloud

guides/common/modules/proc_updating-and-refreshing-red-hat-subscription-manifests.adoc

@@ -4,7 +4,10 @@
 = Updating and refreshing Red Hat subscription manifests
 
 [role="_abstract"]
-Every time that you change a subscription allocation, you must refresh the manifest to reflect these changes.
+You can refresh your Red{nbsp}Hat subscription manifests to keep your subscription allocations up to date.
+Refresh your manifests after renewing, adjusting, or purchasing subscriptions to ensure accurate entitlements in your {Project}.
+
+Every time you change a subscription allocation, you must refresh the manifest to reflect these changes.
 For example, you must refresh the manifest if you take any of the following actions:
 
 * Renewing a subscription
@@ -16,6 +19,10 @@ Alternatively, you can import an updated manifest that contains the changes.
 
 The {ProjectWebUI} provides a notification before the subscription manifest expires.
 
+.Prerequisites
+* A Red{nbsp}Hat subscription manifest is imported to {ProjectServer}.
+For more information, see xref:Importing_a_Red_Hat_Subscription_Manifest_into_Server_{context}[].
+
 .Procedure
 . In the {ProjectWebUI}, ensure the context is set to the organization you want to use.
 . In the {ProjectWebUI}, navigate to *Content* > *Subscriptions*.

guides/common/modules/con_content-delivery-network-structure.adoc → guides/common/modules/ref_red-hat-cdn-structure.adoc

@@ -1,21 +1,15 @@
-:_mod-docs-content-type: CONCEPT
+:_mod-docs-content-type: REFERENCE
 
-[id="Content_Delivery_Network_Structure_{context}"]
-= Content Delivery Network structure
-
-ifdef::katello,orcharhino[]
-[NOTE]
-====
-Information in this section only applies if you consume Red{nbsp}Hat content by using a Red{nbsp}Hat manifest.
-====
-endif::[]
+[id="red-hat-cdn-structure"]
+= Red{nbsp}Hat CDN structure
 
 [role="_abstract"]
-Red{nbsp}Hat Content Delivery Network (CDN), located at `cdn.redhat.com`, is a geographically distributed series of static webservers which include content and errata designed to be used by systems.
-This content can be accessed directly through a system registered by using Subscription Manager or through the {ProjectWebUI}.
-The accessible subset of the CDN is configured through content available to a system by using https://access.redhat.com/management/[Red{nbsp}Hat Subscription Management] or by using {ProjectServer}.
+The Red{nbsp}Hat Content Delivery Network (CDN) is a geographically distributed series of static web servers providing Red{nbsp}Hat content and errata.
+You can access this content directly through Subscription Manager or {ProjectServer}.
 
-Red{nbsp}Hat Content Delivery network is protected by X.509 certificate authentication to ensure that only valid users can access it.
+The Red{nbsp}Hat CDN is located at `cdn.redhat.com`.
+{Project} and Subscription Manager configure which content is accessible to your systems based on your subscription entitlements.
+The Red{nbsp}Hat CDN is protected by X.509 certificate authentication to ensure that only valid users can access it.
 
 .Directory structure of the Red{nbsp}Hat CDN
 ====