diff --git a/modules/hcp-dr-oadp-backup-cp-workload-auto.adoc b/modules/hcp-dr-oadp-backup-cp-workload-auto.adoc
index 9866205296a9..b63d5314dcfa 100644
--- a/modules/hcp-dr-oadp-backup-cp-workload-auto.adoc
+++ b/modules/hcp-dr-oadp-backup-cp-workload-auto.adoc
@@ -2,10 +2,11 @@
 //
 // * hosted_control_planes/hcp-disaster-recovery-oadp-auto.adoc
 
-:_mod-docs-content-type: REFERENCE
+:_mod-docs-content-type: PROCEDURE
 [id="hcp-dr-oadp-backup-cp-workload-auto_{context}"]
 = Backing up the control plane workload
 
+[role="_abstract"]
 You can back up the control plane workload by creating the `Backup` custom resource (CR).
 
 To monitor and observe the backup process, see "Observing the backup and restore process".
@@ -14,23 +15,20 @@ To monitor and observe the backup process, see "Observing the backup and restore
 
 . Create a YAML file that defines the `Backup` CR:
 +
-.Example `backup-control-plane.yaml` file
-[%collapsible]
-====
 [source,yaml]
 ----
 apiVersion: velero.io/v1
 kind: Backup
 metadata:
-  name: <backup_resource_name> <1>
+  name: <backup_resource_name>
   namespace: openshift-adp
   labels:
     velero.io/storage-location: default
 spec:
   hooks: {}
-  includedNamespaces: <2>
-  - <hosted_cluster_namespace> <3>
-  - <hosted_control_plane_namespace> <4>
+  includedNamespaces:
+  - <hosted_cluster_namespace>
+  - <hosted_control_plane_namespace>
   includedResources:
   - sa
   - role
@@ -40,7 +38,7 @@ spec:
   - pv
   - bmh
   - configmap
-  - infraenv <5>
+  - infraenv
   - priorityclasses
   - pdb
   - agents
@@ -62,18 +60,16 @@ spec:
   excludedResources: []
   storageLocation: default
   ttl: 2h0m0s
-  snapshotMoveData: true <6>
-  datamover: "velero" <6>
-  defaultVolumesToFsBackup: false <7>
+  snapshotMoveData: true
+  datamover: "velero"
+  defaultVolumesToFsBackup: false
 ----
-====
-<1> Replace `backup_resource_name` with a name for your `Backup` resource.
-<2> Selects specific namespaces to back up objects from them. You must include your hosted cluster namespace and the hosted control plane namespace.
-<3> Replace `<hosted_cluster_namespace>` with the name of the hosted cluster namespace, for example, `clusters`.
-<4> Replace `<hosted_control_plane_namespace>` with the name of the hosted control plane namespace, for example, `clusters-hosted`.
-<5> You must create the `infraenv` resource in a separate namespace. Do not delete the `infraenv` resource during the backup process.
-<6> Enables the CSI volume snapshots and uploads the control plane workload automatically to the cloud storage.
-<7> Specifies that the `fs-backup` backing up method for persistent volumes (PVs) is not used.
++
+* `metadata.name` specifies the name for your `Backup` resource.
+* `spec.includedNamespaces` specifies namespaces to back up objects from. You must replace `<hosted_cluster_namespace>` with the name of the hosted cluster namespace and replace `<hosted_control_plane_namespace>` with the name of the hosted control plane namespace.
+* `spec.includedResources` includes the `infraenv` value. You must create the `infraenv` resource in a separate namespace. Do not delete the `infraenv` resource during the backup process.
+* `spec.snapshotMoveData: true` and `spec.datamover: velero` enable the CSI volume snapshots and upload the control plane workload automatically to cloud storage.
+* `spec.defaultVolumesToFsBackup` specifies that the `fs-backup` backing up method for persistent volumes (PVs) is not used.
 +
 [NOTE]
 ====