diff --git a/backup_and_restore/application_backup_and_restore/installing/installing-oadp-kubevirt.adoc b/backup_and_restore/application_backup_and_restore/installing/installing-oadp-kubevirt.adoc
index 8fe2f70adff1..13f0630fc8de 100644
--- a/backup_and_restore/application_backup_and_restore/installing/installing-oadp-kubevirt.adoc
+++ b/backup_and_restore/application_backup_and_restore/installing/installing-oadp-kubevirt.adoc
@@ -10,6 +10,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+[role="_abstract"]
 You can install the {oadp-first} with {VirtProductName} by installing the OADP Operator and configuring a backup location. Then, you can install the Data Protection Application.
 
 Back up and restore virtual machines by using the xref:../../../backup_and_restore/index.adoc#application-backup-restore-operations-overview[{oadp-full}].
diff --git a/modules/install-and-configure-oadp-kubevirt.adoc b/modules/install-and-configure-oadp-kubevirt.adoc
index cd1f319aaa56..ce220a7a9a02 100644
--- a/modules/install-and-configure-oadp-kubevirt.adoc
+++ b/modules/install-and-configure-oadp-kubevirt.adoc
@@ -6,6 +6,7 @@
 [id="install-and-configure-oadp-kubevirt_{context}"]
 = Installing and configuring {oadp-short} with {VirtProductName}
 
+[role="_abstract"]
 As a cluster administrator, you install {oadp-short} by installing the {oadp-short} Operator.
 
 The latest version of the {oadp-short} Operator installs link:https://velero.io/docs/v{velero-version}[Velero {velero-version}].
diff --git a/modules/oadp-backup-single-vm.adoc b/modules/oadp-backup-single-vm.adoc
index d8f074bb9c25..b85d4820dda4 100644
--- a/modules/oadp-backup-single-vm.adoc
+++ b/modules/oadp-backup-single-vm.adoc
@@ -7,6 +7,7 @@
 [id="oadp-backup-single-vm_{context}"]
 = Backing up a single VM
 
+[role="_abstract"]
 If you have a namespace with multiple virtual machines (VMs), and want to back up only one of them, you can use the label selector to filter the VM that needs to be included in the backup. You can filter the VM by using the `app: vmname` label.
 
 
diff --git a/modules/oadp-incremental-backup-support.adoc b/modules/oadp-incremental-backup-support.adoc
index dc8eed882d26..bd4c9e57b7e8 100644
--- a/modules/oadp-incremental-backup-support.adoc
+++ b/modules/oadp-incremental-backup-support.adoc
@@ -6,6 +6,7 @@
 [id="oadp-about-incremental-backup-support_{context}"]
 = About incremental back up support
 
+[role="_abstract"]
 {oadp-short} supports incremental backups of `block` and `Filesystem` persistent volumes for both containerized, and {VirtProductName} workloads. The following table summarizes the support for File System Backup (FSB), Container Storage Interface (CSI), and CSI Data Mover:
 
 [cols="5", options="header"]
diff --git a/modules/oadp-restore-single-vm-from-multiple-vm-backup.adoc b/modules/oadp-restore-single-vm-from-multiple-vm-backup.adoc
index a00348299050..763da725f789 100644
--- a/modules/oadp-restore-single-vm-from-multiple-vm-backup.adoc
+++ b/modules/oadp-restore-single-vm-from-multiple-vm-backup.adoc
@@ -7,6 +7,7 @@
 [id="oadp-restore-single-vm-from-multiple-vm-backup_{context}"]
 = Restoring a single VM from a backup of multiple VMs
 
+[role="_abstract"]
 If you have a backup containing multiple virtual machines (VMs), and you want to restore only one VM, you can use the `LabelSelectors` section in the `Restore` CR to select the VM to restore. To ensure that the persistent volume claim (PVC) attached to the VM is correctly restored, and the restored VM is not stuck in a `Provisioning` status, use both the `app: <vm_name>` and the `kubevirt.io/created-by` labels. To match the `kubevirt.io/created-by` label, use the UID of `DataVolume` of the VM.
 
 
diff --git a/modules/oadp-restore-single-vm.adoc b/modules/oadp-restore-single-vm.adoc
index 83b11fa2e21d..f4cd24448817 100644
--- a/modules/oadp-restore-single-vm.adoc
+++ b/modules/oadp-restore-single-vm.adoc
@@ -7,6 +7,7 @@
 [id="oadp-restore-single-vm_{context}"]
 = Restoring a single VM
 
+[role="_abstract"]
 After you have backed up a single virtual machine (VM) by using the label selector in the `Backup` custom resource (CR), you can create a `Restore` CR and point it to the backup. This restore operation restores a single VM.
 
 .Prerequisites
diff --git a/snippets/oadp-windows-vm-backup-fails.adoc b/snippets/oadp-windows-vm-backup-fails.adoc
index be90a1d69017..de377d02e801 100644
--- a/snippets/oadp-windows-vm-backup-fails.adoc
+++ b/snippets/oadp-windows-vm-backup-fails.adoc
@@ -4,6 +4,8 @@
 // * backup_and_restore/application_backup_and_restore/installing/installing-oadp-kubevirt.adoc
 
 :_mod-docs-content-type: SNIPPET
+
+[role="_abstract"]
 [WARNING]
 ====
 If you run a backup of a Microsoft Windows virtual machine (VM) immediately after the VM reboots, the backup might fail with a `PartiallyFailed` error. This is because, immediately after a VM boots, the Microsoft Windows Volume Shadow Copy Service (VSS) and Guest Agent (GA) service are not ready. The VSS and GA service being unready causes the backup to fail. In such a case, retry the backup a few minutes after the VM boots.