diff --git a/virt/vm_networking/virt-networking-overview.adoc b/virt/vm_networking/virt-networking-overview.adoc
index 497527791c..9d984539f0 100644
--- a/virt/vm_networking/virt-networking-overview.adoc
+++ b/virt/vm_networking/virt-networking-overview.adoc
@@ -6,8 +6,8 @@ include::_attributes/common-attributes.adoc[]
 
 toc::[]
 
-{VirtProductName} provides advanced networking functionality by using custom resources and plugins. Virtual machines (VMs) are integrated with {product-title} networking and its ecosystem.
-
+[role="_abstract"]
+To connect Virtual Machines (VMs) to cluster networks, configure default and user-defined networking options in {VirtProductName}.
 
 {VirtProductName} support for single-stack IPv6 clusters is limited to the OVN-Kubernetes localnet and Linux bridge Container Network Interface (CNI) plugins.
 
@@ -51,6 +51,8 @@ include::modules/virt-networking-glossary.adoc[leveloffset=+1]
 [id="default-network-config"]
 == Using the default pod network
 
+To ensure your virtual machines connect reliably using the standard {product-title} networking model, configure the default pod network for cluster-wide connectivity.
+
 xref:../../virt/vm_networking/virt-connecting-vm-to-default-pod-network.adoc#virt-connecting-vm-to-default-pod-network[Connecting a virtual machine to the default pod network]::
 
 Each VM is connected by default to the default internal pod network. You can add or remove network interfaces by editing the VM specification.
@@ -68,6 +70,7 @@ endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
 
 [id="primary-udn-config"]
 == Configuring a primary user-defined network
+To provide isolated and flexible traffic paths for your workloads, configure a primary user-defined network (UDN) that supports multi-namespace connectivity.
 
 xref:../../virt/vm_networking/virt-connecting-vm-to-primary-udn.adoc#virt-connecting-vm-to-primary-udn[Connecting a virtual machine to a primary user-defined network]::
 You can connect a virtual machine (VM) to a user-defined network (UDN) on the primary interface of the VM. The primary UDN replaces the default pod network to connect pods and VMs in selected namespaces.
@@ -162,7 +165,6 @@ You can create a Linux bridge network and attach a VM to the network by performi
 . xref:../../virt/vm_networking/virt-connecting-vm-to-linux-bridge.adoc#configuring-vm-network-interface[Connect the VM to the Linux bridge network] by including the network details in the VM configuration.
 endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
 
-
 //ROSA/OSD supports hot plugging with bridge binding and layer2 OVN-Kubernetes topology
 xref:../../virt/vm_networking/virt-hot-plugging-network-interfaces.adoc#virt-hot-plugging-network-interfaces[Hot plugging secondary network interfaces]::
 
@@ -236,12 +238,11 @@ The following table provides a comparison of features available when using the L
 |===
 endif::openshift-rosa,openshift-dedicated,openshift-rosa-hcp[]
 
-
 [id="service-mesh-integration"]
-== Integrating with OpenShift Service Mesh
+== Integrating with {SMProductName} 
 xref:../../virt/vm_networking/virt-connecting-vm-to-service-mesh.adoc#virt-connecting-vm-to-service-mesh[Connecting a virtual machine to a service mesh]::
 
-{VirtProductName} is integrated with OpenShift Service Mesh. You can monitor, visualize, and control traffic between pods and virtual machines.
+{VirtProductName} is integrated with {SMProductShortName}. You can monitor, visualize, and control traffic between pods and virtual machines.
 
 [id="managing-mac-address-pools"]
 == Managing MAC address pools
@@ -272,3 +273,4 @@ You create a service, associate the service with the VM, and connect to the IP a
 * xref:../../virt/managing_vms/virt-accessing-vm-ssh.adoc#using-secondary-networks-ssh_virt-accessing-vm-ssh[Secondary network]
 +
 You configure a secondary network, attach a VM to the secondary network interface, and connect to its allocated IP address.
+