fix

Author: v-thepet

articles/virtual-network/create-vm-accelerated-networking-cli.md

@@ -174,6 +174,7 @@ Binding to the synthetic NIC that's exposed in the VM is a mandatory requirement
 
 For more information about application binding requirements, see [How Accelerated Networking works in Linux and FreeBSD VMs](./accelerated-networking-how-it-works.md#application-usage).
 
+<a name="enable-accelerated-networking-on-existing-vms"></a>
 ## Manage Accelerated Networking on existing VMs
 
 It's possible to enable Accelerated Networking on an existing VM that doesn't have this feature. The VM must meet the following requirements to support Accelerated Networking:

articles/virtual-network/virtual-network-manage-subnet.md

@@ -98,7 +98,7 @@ You can configure the following settings for a subnet:
 
    | Setting | Description |
    | --- | --- |
-   | **Name** | The name must be unique within the virtual network. For maximum compatibility with other Azure services, use a letter as the first character of the name. For example, Azure Application Gateway won't deploy into a subnet that has a name that starts with a number. |
+   | **Name** | The name must be unique within the virtual network. For maximum compatibility with other Azure services, use a letter as the first character of the name. For example, Azure Application Gateway doesn't deploy into a subnet that has a name that starts with a number. |
    | **Subnet address range** | The range must be unique within the address space and can't overlap with other subnet address ranges in the virtual network. You must specify the address space by using Classless Inter-Domain Routing (CIDR) notation.<br><br>For example, in a virtual network with address space `10.0.0.0/16`, you might define a subnet address space of `10.0.0.0/22`. The smallest range you can specify is `/29`, which provides eight IP addresses for the subnet. Azure reserves the first and last address in each subnet for protocol conformance, and three more addresses for Azure service usage. So defining a subnet with a */29* address range gives three usable IP addresses in the subnet.<br><br>If you plan to connect a virtual network to a virtual private network (VPN) gateway, you must create a gateway subnet. For more information, see [Gateway subnet](../vpn-gateway/vpn-gateway-about-vpn-gateway-settings.md?toc=%2fazure%2fvirtual-network%2ftoc.json#gwsub).|
    | **Add IPv6 address space** | You can create a dual-stack virtual network that supports IPv4 and IPv6 by adding an existing IPv6 address space. Currently, IPv6 isn't fully supported for all services in Azure. For more information, see [Overview of IPv6 for Azure Virtual Network](ip-services/ipv6-overview.md)|
    | **NAT gateway** | To provide network address translation (NAT) to resources on a subnet, you can associate an existing NAT gateway to a subnet. The NAT gateway must exist in the same subscription and location as the virtual network. For more information, see [Virtual network NAT](./nat-gateway/nat-overview.md) and [Quickstart: Create a NAT gateway by using the Azure portal](./nat-gateway/quickstart-create-nat-gateway-portal.md).|

articles/virtual-network/virtual-network-network-interface.md

@@ -280,6 +280,7 @@ Get-AzNetworkInterface -Name myNIC -ResourceGroupName myResourceGroup
 
 You can change most settings for a network interface after you create it.
 
+<a name="change-dns-servers"></a>
 ### Add or change DNS servers
 
 Azure DHCP assigns the DNS server to the network interface within the VM operating system. The network interface can inherit the settings from the virtual network, or use its own unique settings that override the setting for the virtual network. For more information about name resolution settings for a network interface, see [Name resolution for virtual machines](virtual-networks-name-resolution-for-vms-and-role-instances.md).
@@ -363,13 +364,13 @@ $nic | Set-AzNetworkInterface
 IP forwarding enables a VM network interface to:
 
 - Receive network traffic not destined for any of the IP addresses assigned in any of the network interface's IP configurations.
-- Send network traffic with a different source IP address than assigned in any of the network interface's IP configurations.
+- Send network traffic with a different source IP address than was assigned in any of the network interface's IP configurations.
 
 You must enable the setting for every network interface attached to the VM that needs to forward traffic. A VM can forward traffic whether it has multiple network interfaces or a single network interface attached to it.
 
 IP forwarding is typically used with user-defined routes. For more information, see [User-defined routes](virtual-networks-udr-overview.md).
 
-While IP forwarding is an Azure setting, the VM must also run an application that's able to forward the traffic, such as a firewall, WAN optimization, or load balancing application. A VM running network applications is often called a network virtual appliance (NVA). You can view a list of ready-to-deploy NVAs in the [Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps/category/networking?page=1&subcategories=appliances). 
+While IP forwarding is an Azure setting, the VM must also run an application that's able to forward the traffic, such as a firewall, WAN optimization, or load balancing application. A VM that runs network applications is often called a network virtual appliance (NVA). You can view a list of ready-to-deploy NVAs in the [Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps/category/networking?page=1&subcategories=appliances). 
 
 # [Portal](#tab/network-interface-portal)