Update virtual-network-tap-overview.md

Author: AvirupCha

articles/virtual-network/virtual-network-tap-overview.md

@@ -23,7 +23,7 @@ The following diagram shows how virtual network TAP works. You can add a TAP con
 
 ## Prerequisites
 
-Before you can create a virtual network TAP, ensure you've received the confirmation email that you're enrolled in the preview. You must have one or more virtual machines created with [Azure Resource Manager](../azure-resource-manager/management/overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json), and a partner solution for aggregating the TAP traffic in the same Azure region. If you don't have a  partner solution in your virtual network, see [partner solutions](#virtual-network-tap-partner-solutions) to deploy one. 
+You must have one or more virtual machines created with [Azure Resource Manager](../azure-resource-manager/management/overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json), and a partner solution for aggregating the TAP traffic in the same Azure region. If you don't have a  partner solution in your virtual network, see [partner solutions](#virtual-network-tap-partner-solutions) to deploy one. For testing, purpose you can also use any traffic monitoring solution such as Wireshark.
 
 You can use the same virtual network TAP resource to aggregate traffic from multiple network interfaces in the same or different subscriptions. If the monitored network interfaces are in different subscriptions, the subscriptions must be associated to the same Microsoft Entra tenant. Additionally, the monitored network interfaces, and the destination endpoint for aggregating the TAP traffic can be in peered virtual networks in the same region. If you're using this deployment model, ensure that the [virtual network peering](virtual-network-peering-overview.md) is enabled before you configure virtual network TAP.
 
@@ -39,12 +39,13 @@ The accounts you use to apply TAP configuration on network interfaces must be as
 
 ## Public preview limitations
 ### Adding a source:
-- Virtual network TAP only supports virtual machine's (VM) network interface as a mirroring source. All VM SKU **except for v6** are supported but will be supported at GA.
-- Before adding a VM as a source you must **first deploy a virtual network TAP resource** and **then STOP (deallocate) and START the source VM**. This is required only once for any VM that will be added as a source. **If not done, you will get an erorr stating the NIC is not on fastpath**. This is only a requirement for our Public Preview and will not be at GA.
+- Virtual network TAP only supports virtual machine's (VM) network interface as a mirroring source.
+- v6 VM SKU aren't supported as a source. v6 will be supported at GA.
+- Before adding a VM as a source, you must **first deploy a virtual network TAP resource** and **then STOP (deallocate) and START the source VM**. This is required only once for any VM that will be added as a source. **If not done, you will get an erorr stating the NIC is not on fastpath**. At GA, it will not be a requirement.
 
 ### Other Limitations
 - Virtual network TAP supports Load Balancer or VM's network interface as a destination resource for mirrored traffic.
-- Virtual network doesn't support Live Migration. VM set as source for virtual network TAP will have live migration disabled. Live migration will be supported at GA.
+- Virtual network doesn't support Live Migration. Live Migration will be disabled for VMs set as a source. Live migration will be supported at GA.
 - VMs behind a Standard Load Balancer with Floating IP enabled can't be set as a mirroring source. It will be supported at GA.
 - VMs behind Basic Load Balancer can't be set as a mirroring source. Basic Load Balancer is being deprecated.
 - Virtual network doesn't support mirroring of inbound Private Link Service traffic.