Merge pull request #79164 from vhorne/ag-qs-ps

typo in powershell cmdlet, and acro fixes

Author: PRMerger13

articles/application-gateway/quick-create-powershell.md

@@ -1,11 +1,11 @@
 ---
 title: Quickstart - Direct web traffic with Azure Application Gateway - Azure PowerShell | Microsoft Docs
-description: Learn how use Azure PowerShell to create an Azure Application Gateway that directs web traffic to virtual machines in a backend pool.
+description: Learn how to use Azure PowerShell to create an Azure Application Gateway that directs web traffic to virtual machines in a backend pool.
 services: application-gateway
 author: vhorne
 ms.service: application-gateway
 ms.topic: quickstart
-ms.date: 1/11/2019
+ms.date: 06/11/2019
 ms.author: victorh
 ms.custom: mvc
 ---
@@ -31,15 +31,15 @@ If you choose to install and use Azure PowerShell locally, this tutorial require
 
 ### Resource group
 
-In Azure, you allocate related resources to a resource group. You can either use an existing resource group or create a new one. In this example, we will create a new resource group by using the [New-AzResourceGroup](/powershell/module/Az.resources/new-Azresourcegroup) cmdlet as follows: 
+In Azure, you allocate related resources to a resource group. You can either use an existing resource group or create a new one. In this example, you'll create a new resource group by using the [New-AzResourceGroup](/powershell/module/Az.resources/new-Azresourcegroup) cmdlet as follows: 
 
 ```azurepowershell-interactive
 New-AzResourceGroup -Name myResourceGroupAG -Location eastus
 ```
 
 ### Required network resources
 
-For Azure to communicate between the resources that you create, it needs a virtual network.  The application gateway subnet can contain only application gateways. No other resources are allowed.  You can either create a new subnet for Application Gateway or use an existing one. In this example, you create two subnets in this example: one for the application gateway, and another for the backend servers. You can configure the Frontend IP of the Application Gateway to be Public or Private as per your use case. In this example, we will choose a Public Frontend IP.
+For Azure to communicate between the resources that you create, it needs a virtual network.  The application gateway subnet can contain only application gateways. No other resources are allowed.  You can either create a new subnet for Application Gateway or use an existing one. In this example, you create two subnets in this example: one for the application gateway, and another for the backend servers. You can configure the Frontend IP of the Application Gateway to be Public or Private as per your use case. In this example, you'll choose a Public Frontend IP.
 
 1. Create the subnet configurations by calling [New-AzVirtualNetworkSubnetConfig](/powershell/module/Az.network/new-Azvirtualnetworksubnetconfig).
 2. Create the virtual network with the subnet configurations by calling [New-AzVirtualNetwork](/powershell/module/Az.network/new-Azvirtualnetwork). 
@@ -104,7 +104,7 @@ for ($i=1; $i -le 2; $i++)
   Add-AzVMNetworkInterface `
     -VM $vm `
     -Id $nic.Id
-  Set-AzVMBootDiagnostics `
+  Set-AzVMBootDiagnostic `
     -VM $vm `
     -Disable
   New-AzVM -ResourceGroupName myResourceGroupAG -Location EastUS -VM $vm
@@ -214,7 +214,7 @@ New-AzApplicationGateway `
 Although IIS isn't required to create the application gateway, you installed it in this quickstart to verify whether Azure successfully created the application gateway. Use IIS to test the application gateway:
 
 1. Run [Get-AzPublicIPAddress](/powershell/module/Az.network/get-Azpublicipaddress) to get the public IP address of the application gateway. 
-2. Copy and paste the public IP address into the address bar of your browser. When you refresh the browser, you should see the name of the virtual machine. A valid response verifies that the application gateway was successfully created and it is able to successfully connect with the backend.
+2. Copy and paste the public IP address into the address bar of your browser. When you refresh the browser, you should see the name of the virtual machine. A valid response verifies that the application gateway was successfully created and it can successfully connect with the backend.
 
 ```azurepowershell-interactive
 Get-AzPublicIPAddress -ResourceGroupName myResourceGroupAG -Name myAGPublicIPAddress