updates

Author: mbender-ms

includes/load-balancer-multi-ip-cli.md

@@ -10,7 +10,7 @@
  ms.custom: include file
 ---
 
-## Steps to load balance on multiple IP configurations
+## Load balance on multiple IP configurations
 
 To achieve the scenario outlined in this article complete the following steps:
 
@@ -101,6 +101,6 @@ To achieve the scenario outlined in this article complete the following steps:
     az vm create --resource-group contosofabrikam --name VM2 --location westcentralus --os-type linux --nic-names VM2Nic1,VM2Nic2 --vnet-name VNet1 --vnet-subnet-name Subnet1 --availability-set myAvailabilitySet --vm-size Standard_DS3_v2 --storage-account-name mystorageaccount2 --image-urn canonical:UbuntuServer:16.04.0-LTS:latest --admin-username <your username>  --admin-password <your password>
     ```
 
-13. Finally, you must configure DNS resource records to point to the respective frontend IP address of the Load Balancer. You may host your domains in Azure DNS. For more information about using Azure DNS with Load Balancer, see [Using Azure DNS with other Azure services](/azure/dns/dns-for-azure-services)
+13. Finally, you must configure DNS resource records to point to the respective frontend IP address of the Load Balancer. You can host your domains in Azure DNS. For more information about using Azure DNS with Load Balancer, see [Using Azure DNS with other Azure services](/azure/dns/dns-for-azure-services)
 
 

includes/load-balancer-multi-ip-portal.md

@@ -376,13 +376,13 @@ During the creation of the load balancer, you configure:
     | Setting                 | Value                                              |
     | ---                     | ---                                                |
     | **Project details** |   |
-    | Subscription               | Select your subscription.    |    
+    | Subscription               | Select your subscription.   |    
     | Resource group         | Select **load-balancer-rg**. |
     | **Instance details** |   |
     | Name                   | Enter **myLoadBalancer**                                   |
-    | Region         | Select **East US**.                                        |
+    | Region         | Select **East US**.                                       |
     | SKU           | Leave the default **Standard**. |
-    | Type          | Select **Public**.                                        |
+    | Type          | Select **Public**.                                       |
     | Tier          | Leave the default **Regional**. |
 
 4. Select **Next: Frontend IP configuration**.
@@ -403,7 +403,7 @@ During the creation of the load balancer, you configure:
     >
     > For more information on IP prefixes, see [Azure Public IP address prefix](../virtual-network/ip-services/public-ip-address-prefix.md).
     >
-    > In regions with [Availability Zones](../reliability/availability-zones-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json), you have the option to select no-zone (default option), a specific zone, or zone-redundant. The choice will depend on your specific domain failure requirements. In regions without Availability Zones, this field won't appear.</br> For more information on availability zones, see [Availability zones overview](../reliability/availability-zones-overview.md).
+    > In regions with [Availability Zones](../reliability/availability-zones-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json), you can select no-zone (default option), a specific zone, or zone-redundant. The choice depends on your specific domain failure requirements. In regions without Availability Zones, this field won't appear.</br> For more information on availability zones, see [Availability zones overview](../reliability/availability-zones-overview.md).
 
 7. Select **Add**.
 
@@ -509,7 +509,7 @@ During the creation of the load balancer, you configure:
 32. Select **Create**.
 
     > [!NOTE]
-    > In this example we created a NAT gateway to provide outbound Internet access. The outbound rules tab in the configuration is bypassed as it's optional isn't needed with the NAT gateway. For more information on Azure NAT gateway, see [What is Azure Virtual Network NAT?](../virtual-network/nat-gateway/nat-overview.md)
+    > In this example, we created a NAT gateway to provide outbound Internet access. The outbound rules tab in the configuration is bypassed as it's optional and isn't needed with the NAT gateway. For more information on Azure NAT gateway, see [What is Azure Virtual Network NAT?](../virtual-network/nat-gateway/nat-overview.md)
     > For more information about outbound connections in Azure, see [Source Network Address Translation (SNAT) for outbound connections](../load-balancer/load-balancer-outbound-connections.md)
 
 ## Test load balancer
@@ -544,7 +544,7 @@ In this section, you discover the public IP address for each website. You enter
 
 If you're not going to continue to use this application, delete the virtual machines and load balancer with the following steps:
 
-1. In the search box at the top of the portal, enter **Resource group**.  Select **Resource groups** in the search results.
+1. In the search box at the top of the portal, enter **Resource group**. Select **Resource groups** in the search results.
 
 2. Select **load-balancer-rg** in **Resource groups**.
 

includes/load-balancer-multi-ip-powershell.md

@@ -10,12 +10,12 @@
  ms.custom: include file
 ---
 
-## Steps to load balance on multiple IP configurations
+## Load balance on multiple IP configurations
 
 [!INCLUDE [updated-for-az](~/reusable-content/ce-skilling/azure/includes/updated-for-az.md)]
 
-Follow the steps below to achieve the scenario outlined in this article:
-
+Use the following steps to create a load balancer that can balance traffic across multiple IP configurations on a single virtual machine (VM) with Azure PowerShell. This example uses two VMs, but you can use this same process for any number of VMs.
+ 
 1. Install Azure PowerShell. See [How to install and configure Azure PowerShell](/powershell/azure/) for information about installing the latest version of Azure PowerShell, selecting your subscription, and signing in to your account.
 2. Create a resource group using the following settings:
 
@@ -53,7 +53,7 @@ Follow the steps below to achieve the scenario outlined in this article:
 
     You don't need to associate the secondary IP configurations with public IPs in this tutorial. Edit the command to remove the public IP association part.
 
-6. Complete steps 4 through 6 of this article again for VM2. Be sure to replace the VM name to VM2 when doing this. You don't need to create a virtual network for the second VM. You can create a new subnet based on your use case.
+6. Complete steps 4 through 6 again for VM2. Be sure to replace the VM name to `VM2` in code examples. You don't need to create a virtual network for the second VM. You can create a new subnet based on your use case.
 
 7. Create two public IP addresses and store them in the appropriate variables as shown:
 
@@ -100,7 +100,7 @@ Follow the steps below to achieve the scenario outlined in this article:
     Add-AzLoadBalancerRuleConfig -Name HTTP -LoadBalancer $mylb -FrontendIpConfiguration $frontendIP2 -BackendAddressPool $beaddresspool2 -Probe $healthProbe -Protocol Tcp -FrontendPort 80 -BackendPort 80 | Set-AzLoadBalancer
     ```
 
-12. The commands below get the NICs and then add both IP configurations of each secondary NIC to the backend address pool of the load balancer:
+12. The following commands get the NICs and then add both IP configurations of each secondary NIC to the backend address pool of the load balancer:
 
     ```powershell
     $nic1 = Get-AzNetworkInterface -Name "VM1-NIC2" -ResourceGroupName "MyResourcegroup";
@@ -117,5 +117,5 @@ Follow the steps below to achieve the scenario outlined in this article:
     $nic2 | Set-AzNetworkInterface
     ```
 
-13. Finally, you must configure DNS resource records to point to the respective frontend IP address of the Load Balancer. You may host your domains in Azure DNS. For more information about using Azure DNS with Load Balancer, see [Using Azure DNS with other Azure services](/azure/dns/dns-for-azure-services)
+13. Finally, you must configure DNS resource records to point to the respective frontend IP address of the Load Balancer. You can host your domains in Azure DNS. For more information about using Azure DNS with Load Balancer, see [Using Azure DNS with other Azure services](/azure/dns/dns-for-azure-services).