diff --git a/cloud_service/upgrading-cloud/upgrade-cloudsvc-operator.adoc b/cloud_service/upgrading-cloud/upgrade-cloudsvc-operator.adoc
index def9e7dfb28..c79e1437924 100644
--- a/cloud_service/upgrading-cloud/upgrade-cloudsvc-operator.adoc
+++ b/cloud_service/upgrading-cloud/upgrade-cloudsvc-operator.adoc
@@ -12,24 +12,20 @@ Red{nbsp}Hat provides regular service updates for the components that it manages
 
 You must regularly upgrade the version of {product-title-short} on your secured clusters to ensure compatibility with {product-title-managed-short}.
 
+//Preparing to upgrade
 include::modules/prepare-operator-upgrades.adoc[leveloffset=+1]
+
 include::modules/change-collection-method.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
 .Additional resources
 * link:https://docs.openshift.com/container-platform/latest/operators/admin/olm-upgrading-operators.html[Updating installed Operators]
 
-[id="rollback-operator-upgrade-cloud"]
-== Rolling back an Operator upgrade for secured clusters
-
-To roll back an Operator upgrade, you can use either the CLI or the {ocp} web console.
-
-[NOTE]
-====
-On secured clusters, rolling back Operator upgrades is needed only in rare cases, for example, if an issue exists with the secured cluster.
-====
+//Rolling back an Operator upgrade for secured clusters
+include::modules/rollback-operator-upgrade-cloud.adoc[leveloffset=+1]
 
 include::modules/rollback-operator-upgrades-cli.adoc[leveloffset=+2]
+
 include::modules/rollback-operator-upgrades-console.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
@@ -37,10 +33,7 @@ include::modules/rollback-operator-upgrades-console.adoc[leveloffset=+2]
 * link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.16/html/operators/understanding-operators#olm-workflow[Operator Lifecycle Manager workflow]
 * link:https://access.redhat.com/documentation/en-us/openshift_container_platform/4.16/html/operators/administrator-tasks#olm-approving-pending-upgrade_olm-upgrading-operators[Manually approving a pending Operator update]
 
-[id="operator-upgrade-troubleshooting_{context}"]
-== Troubleshooting Operator upgrade issues
-
-[role="_abstract"]
-Follow these instructions to investigate and resolve upgrade-related issues for the {product-title-short} Operator.
+//Troubleshooting Operator upgrade issues
+include::modules/operator-upgrade-troubleshooting.adoc[leveloffset=+1]
 
 include::modules/operator-upgrade-fail-to-deploy.adoc[leveloffset=+2]
\ No newline at end of file
diff --git a/modules/operator-upgrade-troubleshooting.adoc b/modules/operator-upgrade-troubleshooting.adoc
index b6343681715..c6d229352fe 100644
--- a/modules/operator-upgrade-troubleshooting.adoc
+++ b/modules/operator-upgrade-troubleshooting.adoc
@@ -1,6 +1,7 @@
 // Module included in the following assemblies:
 //
 // * upgrading/upgrade-operator.adoc
+// * cloud_service/upgrading-cloud/upgrade-cloudsvc-operator.adoc
 
 :_mod-docs-content-type: CONCEPT
 [id="operator-upgrade-troubleshooting_{context}"]
diff --git a/modules/rollback-operator-upgrade-cloud.adoc b/modules/rollback-operator-upgrade-cloud.adoc
new file mode 100644
index 00000000000..c3348d2beea
--- /dev/null
+++ b/modules/rollback-operator-upgrade-cloud.adoc
@@ -0,0 +1,15 @@
+// Module included in the following assemblies:
+//
+// * cloud_service/upgrading-cloud/upgrade-cloudsvc-operator.adoc
+
+:_mod-docs-content-type: CONCEPT
+[id="rollback-operator-upgrade-cloud_{context}"]
+= Rolling back an Operator upgrade for secured clusters
+
+[role="_abstract"]
+To roll back an Operator upgrade, you can use either the CLI or the {ocp} web console.
+
+[NOTE]
+====
+On secured clusters, you only need to roll back Operator upgrades in rare cases, for example, if an issue exists with the secured cluster.
+====