Merge pull request #228707 from mbender-ms/revert-227606-patch-31

Revert "Update upgrade-basicInternal-standard.md"

Author: prmerger-automator[bot]

articles/load-balancer/upgrade-basicInternal-standard.md

@@ -33,7 +33,6 @@ This article introduces a PowerShell script that creates a Standard Load Balance
 * The Basic Load Balancer needs to be in the same resource group as the backend VMs and NICs.
 * If the Standard load balancer is created in a different region, you won’t be able to associate the VMs existing in the old region to the newly created Standard Load Balancer. To work around this limitation, make sure to create a new VM in the new region.
 * If your Load Balancer doesn't have any frontend IP configuration or backend pool, you're likely to hit an error running the script. Make sure they aren't empty.
-* The amount of available IPs in the subnet where the Basic Load Balancers reside needs to be greater than or equal to the amount of frontend IPs that are associated to the Basic Load Balancers for the script to be suscessful. For example, if your Basic Load Balancer has 5 frontend IPs then you will need to have atleast 5 available IPs in your subnet before running the script.   
 * The script can't migrate Virtual Machine Scale Set from Basic Load Balancer's backend to Standard Load Balancer's backend. For this type of upgrade, see [Upgrade a basic load balancer used with Virtual Machine Scale Sets](./upgrade-basic-standard-virtual-machine-scale-sets.md) for instructions and more information.
 
 ## Change IP allocation method to Static for frontend IP Configuration (Ignore this step if it's already static)