diff --git a/modules/nw-ingress-gateway-api-manage-succession.adoc b/modules/nw-ingress-gateway-api-manage-succession.adoc
index 4ffb76fa74cc..aa6148bcb1bf 100644
--- a/modules/nw-ingress-gateway-api-manage-succession.adoc
+++ b/modules/nw-ingress-gateway-api-manage-succession.adoc
@@ -40,7 +40,7 @@ Backup and restore can fail or result in data loss for any CRD fields that were
 $ oc get crd | grep -F -e gateway.networking.k8s.io -e gateway.networking.x-k8s.io
 ----
 +
-.Example output
+*Example output:*
 +
 [source,terminal]
 ----
diff --git a/modules/update-preparing-evaluate-alerts.adoc b/modules/update-preparing-evaluate-alerts.adoc
index 164794fc98bd..97004e87d027 100644
--- a/modules/update-preparing-evaluate-alerts.adoc
+++ b/modules/update-preparing-evaluate-alerts.adoc
@@ -6,6 +6,9 @@
 [id="update-preparing-evaluate-alerts_{context}"]
 = Reviewing alerts to identify uses of removed APIs
 
+[role="_abstract"]
+Before you update your cluster, review alerts that identify removed API usage so that you can migrate affected workloads and avoid disruptions after the update.
+
 Two alerts fire when an API is in use that will be removed in the next release:
 
 * `APIRemovedInNextReleaseInUse` - for APIs that will be removed in the next {product-title} release.
diff --git a/modules/update-preparing-evaluate-cluster.adoc b/modules/update-preparing-evaluate-cluster.adoc
new file mode 100644
index 000000000000..b6ee85609e2a
--- /dev/null
+++ b/modules/update-preparing-evaluate-cluster.adoc
@@ -0,0 +1,12 @@
+// Module included in the following assemblies:
+//
+// * updating/preparing_for_updates/updating-cluster-prepare.adoc
+
+:_mod-docs-content-type: CONCEPT
+[id="evaluating-cluster-removed-apis_{context}"]
+= Evaluating your cluster for removed APIs
+
+[role="_abstract"]
+Before you update your cluster, evaluate your workloads and integrations for uses of removed APIs so that you can migrate them to supported API versions and avoid disruptions.
+
+There are several methods to help administrators identify where APIs that will be removed are in use. However, {product-title} cannot identify all instances, especially workloads that are idle or external tools that are used. It is the responsibility of the administrator to properly evaluate all workloads and other integrations for instances of removed APIs.
diff --git a/updating/preparing_for_updates/updating-cluster-prepare.adoc b/updating/preparing_for_updates/updating-cluster-prepare.adoc
index da3997da78c2..850f231b666e 100644
--- a/updating/preparing_for_updates/updating-cluster-prepare.adoc
+++ b/updating/preparing_for_updates/updating-cluster-prepare.adoc
@@ -27,10 +27,8 @@ Before you can update your {product-title} 4.19 cluster to 4.20, you must provid
 // Removed Kubernetes APIs
 include::modules/update-preparing-list.adoc[leveloffset=+2]
 
-[id="evaluating-cluster-removed-apis"]
-=== Evaluating your cluster for removed APIs
-
-There are several methods to help administrators identify where APIs that will be removed are in use. However, {product-title} cannot identify all instances, especially workloads that are idle or external tools that are used. It is the responsibility of the administrator to properly evaluate all workloads and other integrations for instances of removed APIs.
+// Evaluating your cluster for removed APIs
+include::modules/update-preparing-evaluate-cluster.adoc[leveloffset=+2]
 
 // Reviewing alerts to identify uses of removed APIs
 include::modules/update-preparing-evaluate-alerts.adoc[leveloffset=+3]