diff --git a/guides/common/assembly_managing-content-views.adoc b/guides/common/assembly_managing-content-views.adoc
index de168ae79f5..318fddbde0b 100644
--- a/guides/common/assembly_managing-content-views.adoc
+++ b/guides/common/assembly_managing-content-views.adoc
@@ -51,7 +51,7 @@ include::modules/proc_creating-a-composite-content-view-by-using-cli.adoc[levelo
 include::modules/con_content-filter-overview.adoc[leveloffset=+1]
 
 ifdef::katello,satellite,almalinux,amazon_linux,centos,oracle_linux,red_hat_enterprise_linux,rocky_linux,suse_linux_enterprise_server[]
-include::modules/con_resolving-package-dependencies.adoc[leveloffset=+1]
+include::modules/con_dependency-solving-for-content-views.adoc[leveloffset=+1]
 
 include::modules/proc_enabling-dependency-solving-for-a-content-view.adoc[leveloffset=+1]
 endif::[]
diff --git a/guides/common/modules/con_composite-content-views-overview.adoc b/guides/common/modules/con_composite-content-views-overview.adoc
index 6446d57320a..7152551318c 100644
--- a/guides/common/modules/con_composite-content-views-overview.adoc
+++ b/guides/common/modules/con_composite-content-views-overview.adoc
@@ -4,10 +4,8 @@
 = Composite content views overview
 
 [role="_abstract"]
-A composite content view combines the content from several content views.
-For example, you might have separate content views to manage an operating system and an application individually.
-You can use a composite content view to merge the contents of both content views into a new repository.
-The repositories for the original content views still exist but a new repository also exists for the combined content.
+A composite content view merges repositories from several content views into one host-facing repository.
+Use it when hosts need content from multiple views, such as an operating system and an application, managed separately.
 
 .Application that supports different database servers
 ====
diff --git a/guides/common/modules/con_content-filter-examples.adoc b/guides/common/modules/con_content-filter-examples.adoc
index f2fcf0d258e..23e5519b3d3 100644
--- a/guides/common/modules/con_content-filter-examples.adoc
+++ b/guides/common/modules/con_content-filter-examples.adoc
@@ -4,7 +4,12 @@
 = Content filter examples
 
 [role="_abstract"]
-Use any of the following examples with the procedure that follows to build custom content filters.
+ifdef::katello,satellite,almalinux,centos,oracle_linux,red_hat_enterprise_linux,rocky_linux[]
+These examples show common content filter configurations for package groups, errata, and module streams that you can adapt when refining a content view.
+endif::[]
+ifdef::debian,suse_linux_enterprise_server,ubuntu[]
+These examples show common content filter configurations for package groups and errata that you can adapt when refining a content view.
+endif::[]
 
 [NOTE]
 ====
diff --git a/guides/common/modules/con_content-filter-overview.adoc b/guides/common/modules/con_content-filter-overview.adoc
index 9c2e7ff39a1..72a3897dfcc 100644
--- a/guides/common/modules/con_content-filter-overview.adoc
+++ b/guides/common/modules/con_content-filter-overview.adoc
@@ -5,12 +5,12 @@
 
 [role="_abstract"]
 ifdef::satellite[]
-Content views also use filters to include or restrict certain Yum content.
+Use content view filters to include or exclude specific Yum packages, errata, and other content types from a published view.
 endif::[]
 ifndef::satellite[]
-Content views also use filters to include or restrict certain Deb and Yum content.
+Use content view filters to include or exclude specific Deb and Yum packages, errata, and other content types from a published view.
 endif::[]
-Without these filters, a content view includes everything from the selected repositories.
+Without filters, a content view includes all content from its selected repositories.
 
 Filter types::
 There are two types of content filters:
diff --git a/guides/common/modules/con_resolving-package-dependencies.adoc b/guides/common/modules/con_dependency-solving-for-content-views.adoc
similarity index 97%
rename from guides/common/modules/con_resolving-package-dependencies.adoc
rename to guides/common/modules/con_dependency-solving-for-content-views.adoc
index 2b8226d8ce0..ed6465fae98 100644
--- a/guides/common/modules/con_resolving-package-dependencies.adoc
+++ b/guides/common/modules/con_dependency-solving-for-content-views.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: CONCEPT
 
-[id="Resolving_Package_Dependencies_{context}"]
-= Resolving package dependencies
+[id="dependency-solving-for-content-views"]
+= Dependency solving for content views
 
 [role="_abstract"]
 {Project} can add dependencies of packages in a content view to the dependent repository when publishing the content view.
diff --git a/guides/common/modules/con_rolling-content-views.adoc b/guides/common/modules/con_rolling-content-views.adoc
index b3d409be617..741892fff7d 100644
--- a/guides/common/modules/con_rolling-content-views.adoc
+++ b/guides/common/modules/con_rolling-content-views.adoc
@@ -4,9 +4,8 @@
 = Rolling content views
 
 [role="_abstract"]
-A rolling content view is a curated subset of content that your hosts can access.
-It is a subset of the Library environment and contains the latest synchronized content from one or multiple repositories.
-You can use a rolling content view to provide a continuous stream of synchronized content to hosts.
+A rolling content view is a curated subset of Library content that hosts can access without publishing or promoting new content view versions.
+Use it to provide a continuous stream of the latest synchronized content from one or more repositories.
 
 When you synchronize repositories to {Project}, all rolling content views that contain them get automatically updated to include the latest changes.
 You do not have to publish and/or promote a rolling content view compared to content views or composite content views.
diff --git a/guides/common/modules/proc_assigning-a-rolling-content-view-to-lifecycle-environments-by-using-cli.adoc b/guides/common/modules/proc_assigning-a-rolling-content-view-to-lifecycle-environments-by-using-cli.adoc
index 2decfa6125f..6a8e5dd49b4 100644
--- a/guides/common/modules/proc_assigning-a-rolling-content-view-to-lifecycle-environments-by-using-cli.adoc
+++ b/guides/common/modules/proc_assigning-a-rolling-content-view-to-lifecycle-environments-by-using-cli.adoc
@@ -4,13 +4,17 @@
 = Assigning a rolling content view to lifecycle environments by using Hammer CLI
 
 [role="_abstract"]
-You can assign your rolling content view to lifecycle environments to limit Library content synchronized to {SmartProxyServers} by using Hammer CLI.
+Assign a rolling content view to lifecycle environments to limit which Library content is synchronized to {SmartProxyServers}.
 
 To consume rolling content views, you must assign them to one or more lifecycle environments.
 By doing so, you expose a subset of Library content to those lifecycle environments.
 {Team} does not recommend assigning a rolling content view to the Library environment itself because it creates duplicate content within Library.
 By using environments other than Library, you can synchronize your rolling content views from {ProjectServer} to any {SmartProxyServers} that are configured to consume the relevant lifecycle environments without the need to synchronize all of Library to {SmartProxyServers}.
 
+.Prerequisites
+* A rolling content view exists in your organization.
+* At least one lifecycle environment other than Library exists in your organization.
+
 .Procedure
 . List all content views:
 +
diff --git a/guides/common/modules/proc_assigning-a-rolling-content-view-to-lifecycle-environments-by-using-web-ui.adoc b/guides/common/modules/proc_assigning-a-rolling-content-view-to-lifecycle-environments-by-using-web-ui.adoc
index c31deb6db25..f19d8d422fd 100644
--- a/guides/common/modules/proc_assigning-a-rolling-content-view-to-lifecycle-environments-by-using-web-ui.adoc
+++ b/guides/common/modules/proc_assigning-a-rolling-content-view-to-lifecycle-environments-by-using-web-ui.adoc
@@ -4,13 +4,17 @@
 = Assigning a rolling content view to lifecycle environments by using {ProjectWebUI}
 
 [role="_abstract"]
-You can assign your rolling content view to lifecycle environments to limit Library content synchronized to {SmartProxyServers} by using {ProjectWebUI}.
+Assign a rolling content view to lifecycle environments to limit which Library content is synchronized to {SmartProxyServers}.
 
 To consume rolling content views, you must assign them to one or more lifecycle environments.
 By doing so, you expose a subset of Library content to those lifecycle environments.
 {Team} does not recommend assigning a rolling content view to the Library environment itself because it creates duplicate content within Library.
 By using environments other than Library, you can synchronize your rolling content views from {ProjectServer} to any {SmartProxyServers} that are configured to consume the relevant lifecycle environments without the need to synchronize all of Library to {SmartProxyServers}.
 
+.Prerequisites
+* A rolling content view exists in your organization.
+* At least one lifecycle environment other than Library exists in your organization.
+
 .Procedure
 . In the {ProjectWebUI}, navigate to *Content* > *Lifecycle* > *Content Views*.
 . Select your rolling content view.
diff --git a/guides/common/modules/proc_comparing-content-view-versions.adoc b/guides/common/modules/proc_comparing-content-view-versions.adoc
index 8f7be96d826..aa27e2b39f5 100644
--- a/guides/common/modules/proc_comparing-content-view-versions.adoc
+++ b/guides/common/modules/proc_comparing-content-view-versions.adoc
@@ -4,7 +4,10 @@
 = Comparing content view versions
 
 [role="_abstract"]
-Use this procedure to compare content view version functionality for {Project}.
+Compare two content view versions to identify added, removed, or changed packages, errata, and other content between versions.
+
+.Prerequisites
+* The content view has at least two published versions.
 
 .Procedure
 . In the {ProjectWebUI}, navigate to *Content* > *Lifecycle* > *Content Views*.
diff --git a/guides/common/modules/proc_copying-a-content-view-by-using-cli.adoc b/guides/common/modules/proc_copying-a-content-view-by-using-cli.adoc
index 616f3a69f4d..cfeb51338bb 100644
--- a/guides/common/modules/proc_copying-a-content-view-by-using-cli.adoc
+++ b/guides/common/modules/proc_copying-a-content-view-by-using-cli.adoc
@@ -4,7 +4,7 @@
 = Copying a content view by using Hammer CLI
 
 [role="_abstract"]
-You can copy an existing content view into a new content view by using Hammer CLI.
+Copy an existing content view to create a content view based on its repositories and filters without reconfiguring them from scratch.
 
 [NOTE]
 ====
diff --git a/guides/common/modules/proc_copying-a-content-view-by-using-web-ui.adoc b/guides/common/modules/proc_copying-a-content-view-by-using-web-ui.adoc
index 1b3c9b7618f..4e3bd22583a 100644
--- a/guides/common/modules/proc_copying-a-content-view-by-using-web-ui.adoc
+++ b/guides/common/modules/proc_copying-a-content-view-by-using-web-ui.adoc
@@ -4,7 +4,7 @@
 = Copying a content view by using {ProjectWebUI}
 
 [role="_abstract"]
-You can copy an existing content view into a new content view by using {ProjectWebUI}.
+Copy an existing content view to create a content view based on its repositories and filters without reconfiguring them from scratch.
 
 [NOTE]
 ====
diff --git a/guides/common/modules/proc_creating-a-composite-content-view-by-using-cli.adoc b/guides/common/modules/proc_creating-a-composite-content-view-by-using-cli.adoc
index c5ee66354b5..4243d8cd003 100644
--- a/guides/common/modules/proc_creating-a-composite-content-view-by-using-cli.adoc
+++ b/guides/common/modules/proc_creating-a-composite-content-view-by-using-cli.adoc
@@ -4,7 +4,10 @@
 = Creating a composite content view by using Hammer CLI
 
 [role="_abstract"]
-Use this procedure to create a composite content view by using Hammer CLI.
+Create a composite content view to merge repositories from multiple content views into a single host-facing repository.
+
+.Prerequisites
+* The content views that you want to combine are published.
 
 .Procedure
 . Before you create the composite content views, list the version IDs for your existing content views:
diff --git a/guides/common/modules/proc_creating-a-composite-content-view-by-using-web-ui.adoc b/guides/common/modules/proc_creating-a-composite-content-view-by-using-web-ui.adoc
index fe86a376133..938a9c0ef5b 100644
--- a/guides/common/modules/proc_creating-a-composite-content-view-by-using-web-ui.adoc
+++ b/guides/common/modules/proc_creating-a-composite-content-view-by-using-web-ui.adoc
@@ -4,7 +4,10 @@
 = Creating a composite content view by using {ProjectWebUI}
 
 [role="_abstract"]
-Use this procedure to create a composite content view by using {ProjectWebUI}.
+Create a composite content view to merge repositories from multiple content views into a single host-facing repository.
+
+.Prerequisites
+* The content views that you want to combine are published.
 
 .Procedure
 . In the {ProjectWebUI}, navigate to *Content* > *Lifecycle* > *Content Views*.
diff --git a/guides/common/modules/proc_creating-a-content-view-by-using-cli.adoc b/guides/common/modules/proc_creating-a-content-view-by-using-cli.adoc
index 97ae0fccde4..bcf7a8a1ebf 100644
--- a/guides/common/modules/proc_creating-a-content-view-by-using-cli.adoc
+++ b/guides/common/modules/proc_creating-a-content-view-by-using-cli.adoc
@@ -4,13 +4,16 @@
 = Creating a content view by using Hammer CLI
 
 [role="_abstract"]
-Use this procedure to create a content view by using Hammer CLI.
+Create a content view to define which repositories and content your hosts can access through lifecycle environments.
 
 ifdef::katello,satellite,almalinux,amazon_linux,centos,oracle_linux,red_hat_enterprise_linux,rocky_linux,suse_linux_enterprise_server[]
 While you can stipulate whether you want to resolve any package dependencies on a content view by content view basis, you might want to change the default {Project} settings to enable or disable package resolution for all content views.
-For more information, see xref:Resolving_Package_Dependencies_{context}[].
+For more information, see xref:dependency-solving-for-content-views[].
 endif::[]
 
+.Prerequisites
+* At least one repository is available in your organization.
+
 .Procedure
 . Obtain a list of repository IDs:
 +
diff --git a/guides/common/modules/proc_creating-a-content-view-by-using-web-ui.adoc b/guides/common/modules/proc_creating-a-content-view-by-using-web-ui.adoc
index 27738cb8546..39655ba99e7 100644
--- a/guides/common/modules/proc_creating-a-content-view-by-using-web-ui.adoc
+++ b/guides/common/modules/proc_creating-a-content-view-by-using-web-ui.adoc
@@ -4,13 +4,16 @@
 = Creating a content view by using {ProjectWebUI}
 
 [role="_abstract"]
-Use this procedure to create a content view by using the {ProjectWebUI}.
+Create a content view to define which repositories and content your hosts can access through lifecycle environments.
 
 ifdef::katello,satellite,almalinux,amazon_linux,centos,oracle_linux,red_hat_enterprise_linux,rocky_linux,suse_linux_enterprise_server[]
 While you can stipulate whether you want to resolve any package dependencies on a content view by content view basis, you might want to change the default {Project} settings to enable or disable package resolution for all content views.
-For more information, see xref:Resolving_Package_Dependencies_{context}[].
+For more information, see xref:dependency-solving-for-content-views[].
 endif::[]
 
+.Prerequisites
+* At least one repository is available in your organization.
+
 .Procedure
 . In the {ProjectWebUI}, navigate to *Content* > *Lifecycle* > *Content Views*.
 . Click *Create content view*.
diff --git a/guides/common/modules/proc_creating-a-content-view-filter-by-using-cli.adoc b/guides/common/modules/proc_creating-a-content-view-filter-by-using-cli.adoc
index 91e9373c300..4e2b8591373 100644
--- a/guides/common/modules/proc_creating-a-content-view-filter-by-using-cli.adoc
+++ b/guides/common/modules/proc_creating-a-content-view-filter-by-using-cli.adoc
@@ -6,6 +6,10 @@
 [role="_abstract"]
 You can use Hammer CLI to create content view filters to include or exclude specific content units like packages, errata, or container image tags.
 
+.Prerequisites
+* You have created a content view with the repositories you want to filter.
+For more information, see xref:creating-a-content-view-by-using-cli[].
+
 .Procedure
 . Add a filter to the content view.
 Use the `--inclusion false` option to set the filter to an Exclude filter:
diff --git a/guides/common/modules/proc_creating-a-content-view-filter-by-using-web-ui.adoc b/guides/common/modules/proc_creating-a-content-view-filter-by-using-web-ui.adoc
index d632c058f1b..e4c040bc7b1 100644
--- a/guides/common/modules/proc_creating-a-content-view-filter-by-using-web-ui.adoc
+++ b/guides/common/modules/proc_creating-a-content-view-filter-by-using-web-ui.adoc
@@ -4,10 +4,15 @@
 = Creating a content view filter by using {ProjectWebUI}
 
 [role="_abstract"]
-You can filter content views containing {client-content-type} content to include or exclude specific packages or errata.
-Package filters are based on a combination of the _name_, _version_, and _architecture_.
+Create content view filters to include or exclude specific packages, errata, and other content types from a content view.
+Package filters match content by name, version, and architecture.
+
 For examples of how to build a filter, see xref:Content_Filter_Examples_{context}[].
 
+.Prerequisites
+* You have created a content view with the repositories you want to filter.
+For more information, see xref:creating-a-content-view-by-using-web-ui[].
+
 .Procedure
 . In the {ProjectWebUI}, navigate to *Content* > *Lifecycle* > *Content Views*.
 . Select a content view.
diff --git a/guides/common/modules/proc_creating-a-rolling-content-view-by-using-cli.adoc b/guides/common/modules/proc_creating-a-rolling-content-view-by-using-cli.adoc
index d07138b754d..19500fcc61f 100644
--- a/guides/common/modules/proc_creating-a-rolling-content-view-by-using-cli.adoc
+++ b/guides/common/modules/proc_creating-a-rolling-content-view-by-using-cli.adoc
@@ -4,7 +4,10 @@
 = Creating a rolling content view by using Hammer CLI
 
 [role="_abstract"]
-You can create a rolling content view by using Hammer CLI.
+Create a rolling content view to give hosts continuous access to the latest synchronized content without publishing new content view versions.
+
+.Prerequisites
+* At least one repository is synchronized to your organization.
 
 .Procedure
 . List all available lifecycle environments:
diff --git a/guides/common/modules/proc_creating-a-rolling-content-view-by-using-web-ui.adoc b/guides/common/modules/proc_creating-a-rolling-content-view-by-using-web-ui.adoc
index f512a064e4f..aaa5eb6d937 100644
--- a/guides/common/modules/proc_creating-a-rolling-content-view-by-using-web-ui.adoc
+++ b/guides/common/modules/proc_creating-a-rolling-content-view-by-using-web-ui.adoc
@@ -4,7 +4,10 @@
 = Creating a rolling content view by using {ProjectWebUI}
 
 [role="_abstract"]
-You can create a rolling content view by using {ProjectWebUI}.
+Create a rolling content view to give hosts continuous access to the latest synchronized content without publishing new content view versions.
+
+.Prerequisites
+* At least one repository is synchronized to your organization.
 
 .Procedure
 . In the {ProjectWebUI}, navigate to *Content* > *Lifecycle* > *Content Views*.
diff --git a/guides/common/modules/proc_deleting-multiple-content-view-versions-by-using-web-ui.adoc b/guides/common/modules/proc_deleting-multiple-content-view-versions-by-using-web-ui.adoc
index 983d52ff85c..19821d74c62 100644
--- a/guides/common/modules/proc_deleting-multiple-content-view-versions-by-using-web-ui.adoc
+++ b/guides/common/modules/proc_deleting-multiple-content-view-versions-by-using-web-ui.adoc
@@ -4,7 +4,10 @@
 = Deleting multiple content view versions by using {ProjectWebUI}
 
 [role="_abstract"]
-You can delete multiple content view versions simultaneously by using {ProjectWebUI}.
+Delete multiple content view versions at once to remove obsolete snapshots and free storage on {ProjectServer}.
+
+.Prerequisites
+* Your {Project} account has a role that grants the `promote_or_remove_content_views` permission.
 
 .Procedure
 . In the {ProjectWebUI}, navigate to *Content* > *Lifecycle* > *Content Views*.
diff --git a/guides/common/modules/proc_distributing-archived-content-view-versions.adoc b/guides/common/modules/proc_distributing-archived-content-view-versions.adoc
index 931cc4f687e..e77d6651a3e 100644
--- a/guides/common/modules/proc_distributing-archived-content-view-versions.adoc
+++ b/guides/common/modules/proc_distributing-archived-content-view-versions.adoc
@@ -4,8 +4,10 @@
 = Distributing archived content view versions
 
 [role="_abstract"]
-The setting *Distribute archived content view versions* enables hosting of non-promoted content view version repositories in the {Project} content web application along with other repositories.
-This is useful while debugging to see what content is present in your content view versions.
+Enable distribution of archived content view versions when you need access to repositories from published versions that are not currently promoted, such as for debugging.
+
+.Prerequisites
+* Your {Project} account has a role that grants the `view_settings` and `edit_settings` permissions.
 
 .Procedure
 . In the {ProjectWebUI}, navigate to *Administer* > *Settings*.
diff --git a/guides/common/modules/proc_enabling-dependency-solving-for-a-content-view.adoc b/guides/common/modules/proc_enabling-dependency-solving-for-a-content-view.adoc
index 2f9f233b964..861806f1f9d 100644
--- a/guides/common/modules/proc_enabling-dependency-solving-for-a-content-view.adoc
+++ b/guides/common/modules/proc_enabling-dependency-solving-for-a-content-view.adoc
@@ -4,11 +4,10 @@
 = Enabling dependency solving for a content view
 
 [role="_abstract"]
-Use this procedure to enable dependency solving for a content view.
+Enable dependency solving on a content view when you need {Project} to include package dependencies during publication, such as when adding a single package incrementally.
 
 .Prerequisites
-* Dependency solving is useful only in limited contexts.
-Before enabling it, ensure you read and understand xref:Resolving_Package_Dependencies_{context}[]
+* You have reviewed xref:dependency-solving-for-content-views[] to determine whether dependency solving is appropriate for your content view.
 
 .Procedure
 . In the {ProjectWebUI}, navigate to *Content* > *Lifecycle* > *Content Views*.
diff --git a/guides/common/modules/proc_promoting-a-content-view-by-using-cli.adoc b/guides/common/modules/proc_promoting-a-content-view-by-using-cli.adoc
index 5d2ee15776b..04425b37ba8 100644
--- a/guides/common/modules/proc_promoting-a-content-view-by-using-cli.adoc
+++ b/guides/common/modules/proc_promoting-a-content-view-by-using-cli.adoc
@@ -4,10 +4,11 @@
 = Promoting a content view by using Hammer CLI
 
 [role="_abstract"]
-Use this procedure to promote content views across different lifecycle environments by using Hammer CLI.
+Promote a content view to the next lifecycle environment to make its published content available to hosts in that environment.
 
 .Prerequisites
 * Your {Project} account has a role that grants the `promote_or_remove_content_views` and `promote_or_remove_content_views_to_environment` permissions.
+* The content view has at least one published version.
 
 .Procedure
 * Promote the content view to a lifecycle environment:
diff --git a/guides/common/modules/proc_promoting-a-content-view-by-using-web-ui.adoc b/guides/common/modules/proc_promoting-a-content-view-by-using-web-ui.adoc
index e52175ce29a..73f6f913322 100644
--- a/guides/common/modules/proc_promoting-a-content-view-by-using-web-ui.adoc
+++ b/guides/common/modules/proc_promoting-a-content-view-by-using-web-ui.adoc
@@ -4,10 +4,11 @@
 = Promoting a content view by using {ProjectWebUI}
 
 [role="_abstract"]
-Use this procedure to promote content views across different lifecycle environments by using {ProjectWebUI}.
+Promote a content view to the next lifecycle environment to make its published content available to hosts in that environment.
 
 .Prerequisites
 * Your {Project} account has a role that grants the `promote_or_remove_content_views` and `promote_or_remove_content_views_to_environment` permissions.
+* The content view has at least one published version.
 
 .Procedure
 . In the {ProjectWebUI}, navigate to *Content* > *Lifecycle* > *Content Views*.
diff --git a/guides/common/modules/proc_promoting-a-content-view-to-all-environments-in-an-organization.adoc b/guides/common/modules/proc_promoting-a-content-view-to-all-environments-in-an-organization.adoc
index 26939a68d9b..eb701e0e9b9 100644
--- a/guides/common/modules/proc_promoting-a-content-view-to-all-environments-in-an-organization.adoc
+++ b/guides/common/modules/proc_promoting-a-content-view-to-all-environments-in-an-organization.adoc
@@ -8,6 +8,7 @@ You can promote content views across all lifecycle environments within an organi
 
 .Prerequisites
 * Your {Project} account has a role that grants the `promote_or_remove_content_views` and `promote_or_remove_content_views_to_environment` permissions.
+* The content view version that you want to promote is published.
 
 .Procedure
 * Promote content views across all lifecycle environments within an organization:
diff --git a/guides/common/modules/proc_publishing-and-promoting-a-content-view-by-using-mcp.adoc b/guides/common/modules/proc_publishing-and-promoting-a-content-view-by-using-mcp.adoc
index bb35a1f64a4..52dce402975 100644
--- a/guides/common/modules/proc_publishing-and-promoting-a-content-view-by-using-mcp.adoc
+++ b/guides/common/modules/proc_publishing-and-promoting-a-content-view-by-using-mcp.adoc
@@ -10,6 +10,10 @@ include::snip_warning-ai-output-review.adoc[]
 :FeatureName: The MCP server for {Project} 
 include::snip_technology-preview.adoc[]
 
+.Prerequisites
+* The MCP server for {Project} is deployed and configured to allow content view publish and promote actions.
+For more information, see {ManagingHostsDocURL}deploying-the-mcp-server-for-{project-context}[Deploying the MCP server for {Project}] in _{ManagingHostsDocTitle}_.
+
 .Procedure
 . Allow the MCP server to trigger content view publish and promote actions:
 +
diff --git a/guides/common/modules/proc_synchronizing-a-content-view-to-a-smart-proxy-server.adoc b/guides/common/modules/proc_synchronizing-a-content-view-to-a-smart-proxy-server.adoc
index 93556a05339..b954e79b4fa 100644
--- a/guides/common/modules/proc_synchronizing-a-content-view-to-a-smart-proxy-server.adoc
+++ b/guides/common/modules/proc_synchronizing-a-content-view-to-a-smart-proxy-server.adoc
@@ -7,6 +7,9 @@
 In the {ProjectWebUI}, you can only synchronize all selected lifecycle environments simultaneously.
 If you need to synchronize smaller items, such as individual lifecycle environments, single content views, and single repositories, use the Hammer CLI.
 
+.Prerequisites
+* The content view is published and promoted to a lifecycle environment that the {SmartProxyServer} synchronizes.
+
 .Procedure
 * Synchronize a content view to your {SmartProxyServer}:
 +
diff --git a/guides/common/modules/proc_viewing-module-streams-by-using-cli.adoc b/guides/common/modules/proc_viewing-module-streams-by-using-cli.adoc
index 7243c12af73..d35414a706b 100644
--- a/guides/common/modules/proc_viewing-module-streams-by-using-cli.adoc
+++ b/guides/common/modules/proc_viewing-module-streams-by-using-cli.adoc
@@ -4,7 +4,10 @@
 = Viewing module streams by using Hammer CLI
 
 [role="_abstract"]
-In {Project}, you can view the module streams of the repositories in your content views by using Hammer CLI.
+View module streams in your content views to verify which modular Yum content is included before you publish or promote a content view.
+
+.Prerequisites
+* Your organization includes repositories with module streams.
 
 .Procedure
 . List all organizations:
diff --git a/guides/common/modules/proc_viewing-module-streams-by-using-web-ui.adoc b/guides/common/modules/proc_viewing-module-streams-by-using-web-ui.adoc
index ce0c4283fe2..81bbfc882ec 100644
--- a/guides/common/modules/proc_viewing-module-streams-by-using-web-ui.adoc
+++ b/guides/common/modules/proc_viewing-module-streams-by-using-web-ui.adoc
@@ -4,7 +4,10 @@
 = Viewing module streams by using {ProjectWebUI}
 
 [role="_abstract"]
-You can view the module streams of the repositories in your content views by using {ProjectWebUI}.
+View module streams in your content views to verify which modular Yum content is included before you publish or promote a content view.
+
+.Prerequisites
+* The content view has at least one published version that includes modular repositories.
 
 .Procedure
 . In the {ProjectWebUI}, *Content* > *Lifecycle* > *Content Views*.
diff --git a/guides/common/modules/ref_best-practices-for-content-views.adoc b/guides/common/modules/ref_best-practices-for-content-views.adoc
index 5a0bda25312..daa8b9e802d 100644
--- a/guides/common/modules/ref_best-practices-for-content-views.adoc
+++ b/guides/common/modules/ref_best-practices-for-content-views.adoc
@@ -4,7 +4,7 @@
 = Best practices for content views
 
 [role="_abstract"]
-{Team} recommends you follow these practices for content views.
+{Team} recommends you apply these practices when you plan, publish, and maintain content views to reduce administrative overhead and keep host content consistent.
 
 * Content views that bundle content, such as {client-os} and additional software like `Apache-2.4` or `PostgreSQL-16.2`, are easier to maintain.
 Content views that are too small require more maintenance.
diff --git a/guides/common/modules/ref_workflow-for-creating-content-views.adoc b/guides/common/modules/ref_workflow-for-creating-content-views.adoc
index 6bea1618439..dd6497bbe59 100644
--- a/guides/common/modules/ref_workflow-for-creating-content-views.adoc
+++ b/guides/common/modules/ref_workflow-for-creating-content-views.adoc
@@ -14,7 +14,7 @@ The general workflow for creating content views for filtering and creating snaps
 For more information, see xref:Content_Filter_Examples_{context}[].
 . Optional: Resolve any package dependencies for a content view.
 ifdef::katello,satellite,almalinux,amazon_linux,centos,oracle_linux,red_hat_enterprise_linux,rocky_linux,suse_linux_enterprise_server[]
-For more information, see xref:Resolving_Package_Dependencies_{context}[].
+For more information, see xref:dependency-solving-for-content-views[].
 endif::[]
 . Publish the content view.
 . Optional: Promote the content view to another environment.