diff --git a/modules/virt-about-upgrading-virt.adoc b/modules/virt-about-upgrading-virt.adoc
index a0924e5eb4ac..d55c44d7c535 100644
--- a/modules/virt-about-upgrading-virt.adoc
+++ b/modules/virt-about-upgrading-virt.adoc
@@ -3,6 +3,7 @@
 // * virt/updating/upgrading-virt.adoc
 
 :_mod-docs-content-type: CONCEPT
+include::_attributes/common-attributes.adoc[]
 [id="virt-about-upgrading-virt_{context}"]
 = About updating {VirtProductName}
 
@@ -32,6 +33,9 @@ Each minor version of {VirtProductName} is supported only if you run the corresp
 [id="what-to-expect_{context}"]
 == What to expect
 
+[role="_abstract"]
+This topic helps you understand what happens during an {VirtProductName} update, including expected completion time and preservation of data.
+
 * The amount of time an update takes to complete depends on your network
 connection. Most automatic updates complete within fifteen minutes.
 
@@ -59,6 +63,9 @@ endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
 [id="how-updates-work_{context}"]
 == How updates work
 
+[role="_abstract"]
+This topic helps you understand how the {VirtProductName} Operator is managed and updated using the Operator Lifecycle Manager (OLM).
+
 * Operator Lifecycle Manager (OLM) manages the lifecycle of the {VirtProductName} Operator. The Marketplace Operator, which is deployed during {product-title} installation, makes external Operators available to your cluster.
 
 * OLM provides z-stream and minor version updates for {VirtProductName}. Minor version updates become available when you update {product-title} to the next minor version. You cannot update {VirtProductName} to the next minor version without first updating {product-title}.