binding change

Author: Amelia Shull

articles/virtual-network/accelerated-networking-overview.md

@@ -106,7 +106,7 @@ If you use a custom image that supports Accelerated Networking, make sure you me
 Any custom image supporting Accelerated Networking must include drivers that enable Single Root I/O Virtualization for the network interface cards (NIC) which are used on Azure platforms. This hardware list includes NVIDIA ConnectX-3, ConnectX-4 Lx, ConnectX-5 and the [Microsoft Azure Network Adapter (MANA)](https://learn.microsoft.com/en-us/azure/virtual-network/accelerated-networking-mana-overview). Download and install the latest versions of these drivers into your custom image.
 
 #### Dynamic binding and revocation of virtual function
-Binding to the synthetic NIC that's exposed in the VM is a mandatory requirement for all applications that take advantage of Accelerated Networking. If an application runs directly over the VF NIC, it doesn't receive all packets that are destined to the VM, because some packets show up over the synthetic interface. You must run an application over the synthetic NIC to guarantee that the application receives all packets that are destined to it. Binding to the synthetic NIC also ensures that the application keeps running even if the VF is revoked during host servicing.
+Accelerated Networking requires guest OS images to properly handle the virtual function being removed or added dynamically. Scenarios such as host maintenance or live migration will result in dynamic revocation of the virtual function and restoration after the maintenance event. Additionally, applications must ensure that they bind to the synthetic device and not the virtual function in order to maintain network connectivity during these events. 
 
 For more information about application binding requirements, see [How Accelerated Networking works in Linux and FreeBSD VMs](./create-vm-accelerated-networking-cli?tabs=windows#handle-dynamic-binding-and-revocation-of-virtual-function).