Update abstract tags using Claude

Author: abrennan89

modules/deleting-a-namespace-using-the-web-console.adoc

@@ -6,6 +6,7 @@
 [id="deleting-a-namespace-using-the-web-console_{context}"]
 = Deleting a namespace using the web console
 
+[role="_abstract"]
 You can delete a namespace by using the {product-title} web console.
 
 .Prerequisites

modules/migrating-to-virt.adoc

@@ -6,6 +6,7 @@
 [id="migrating-to-virt_{context}"]
 = Migrating to {VirtProductName}
 
+[role="_abstract"]
 To migrate virtual machines from an external provider such as {vmw-first}, {rh-openstack-first}, Red Hat Virtualization, or another {product-title} cluster, use the {mtv-first}. You can also migrate Open Virtual Appliance (OVA) files created by {vmw-full}.
 
 [NOTE]

modules/olm-deleting-operators-from-a-cluster-using-web-console.adoc

@@ -9,6 +9,7 @@
 [id="olm-deleting-operators-from-a-cluster-using-web-console_{context}"]
 = Deleting Operators from a cluster using the web console
 
+[role="_abstract"]
 Cluster administrators can delete installed Operators from a selected namespace by using the web console.
 
 .Prerequisites

modules/virt-creating-vm-cloned-pvc-data-volume-template.adoc

@@ -6,6 +6,7 @@
 [id="virt-creating-vm-cloning-pvc-data-volume-template_{context}"]
 = Creating a VM from a cloned PVC by using a data volume template
 
+[role="_abstract"]
 You can create a virtual machine (VM) that clones the persistent volume claim (PVC) of an existing VM by using a data volume template. This method creates a data volume whose lifecycle is independent on the original VM.
 
 .Prerequisites

modules/virt-customizing-vm-template-web.adoc

@@ -6,6 +6,7 @@
 [id="virt-customizing-vm-template-web_{context}"]
 = Removing a deprecated designation from a customized VM template by using the web console
 
+[role="_abstract"]
 You can customize an existing virtual machine (VM) template by modifying the VM or template parameters, such as data sources, cloud-init, or SSH keys, before you start the VM. If you customize a template by copying it and including all of its labels and annotations, the customized template is marked as deprecated when a new version of the Scheduling, Scale, and Performance (SSP) Operator is deployed.
 
 You can remove the deprecated designation from the customized template.

virt/about_virt/about-virt.adoc

@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+[role="_abstract"]
 Learn about {VirtProductName}'s capabilities and support scope.
 
 include::modules/virt-what-you-can-do-with-virt.adoc[leveloffset=+1]

virt/about_virt/virt-architecture.adoc

@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+[role="_abstract"]
 The Operator Lifecycle Manager (OLM) deploys operator pods for each component of {VirtProductName}:
 
 * Compute: `virt-operator`

virt/about_virt/virt-security-policies.adoc

@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+[role="_abstract"]
 Learn about {VirtProductName} security and authorization.
 
 .Key points

virt/about_virt/virt-supported-limits.adoc

@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+[role="_abstract"]
 You can refer to tested object maximums when planning your {product-title} environment for {VirtProductName}. However, approaching the maximum values can reduce performance and increase latency. Ensure that you plan for your specific use case and consider all factors that can impact cluster scaling.
 
 For more information about cluster configuration and options that impact performance, see the link:https://access.redhat.com/articles/6994974[{VirtProductName} - Tuning & Scaling Guide] in the Red{nbsp}Hat Knowledgebase.

virt/creating_vm/virt-creating-vms-from-templates.adoc

@@ -6,6 +6,7 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
+[role="_abstract"]
 You can create virtual machines (VMs) from Red Hat templates by using the {product-title} web console.
 
 [id="virt-about-templates"]