Update upgrade-InternalBasic-To-PublicStandard.md

Author: irenehua

articles/load-balancer/upgrade-InternalBasic-To-PublicStandard.md

@@ -16,7 +16,6 @@ There are four stages in a upgrade:
 
 1. Migrate the configuration to Standard Public Load Balancer
 2. Add VMs to backend pools of Standard Public Load Balancer
-3. Create an outbound rule on the Load Balancer for outbound connection
 4. Set up NSG rules for Subnet/VMs that should be refrained from/to the Internet
 
 This article covers configuration migration. Adding VMs to backend pools may vary depending on your specific environment. However, some high-level, general recommendations [are provided](#add-vms-to-backend-pools-of-standard-load-balancer).
@@ -27,6 +26,7 @@ An Azure PowerShell script is available that does the following:
 
 * Creates a Standard SKU Public Load Balancer in the resource group and location that you specify.
 * Seamlessly copies the configurations of the Basic SKU Internal Load Balancer to the newly create Standard Public Load Balancer.
+* Creates an outbound rule which enables egress connectivity.
 
 ### Caveats\Limitations
 
@@ -37,7 +37,7 @@ An Azure PowerShell script is available that does the following:
 
 ## Download the script
 
-Download the migration script from the  [PowerShell Gallery](https://www.powershellgallery.com/packages/AzurePublicLBUpgrade/1.0).
+Download the migration script from the  [PowerShell Gallery](https://www.powershellgallery.com/packages/AzureLBUpgrade/2.0).
 ## Use the script
 
 There are two options for you depending on your local PowerShell environment setup and preferences: