Updates from PMs

Author: mbender-ms

articles/load-balancer/load-balancer-basic-upgrade-guidance.md

@@ -14,13 +14,13 @@ ms.date: 09/19/2022
 In this article, we'll discuss guidance for upgrading your Basic Load Balancer instances to Standard Load Balancer. Standard Load Balancer is recommend for all production instances and provides many [key differences](#basic-load-balancer-sku-vs-standard-load-balancer-sku) to your infrastructure.
 ## Steps to complete the upgrade
 
-We recommend the following approach to upgrade to Standard Load Balancer:
+We recommend the following approach for upgrading to Standard Load Balancer:
 
 1. Learn about some of the [key differences](#basic-load-balancer-sku-vs-standard-load-balancer-sku) between Basic Load Balancer and Standard Load Balancer. 
-1. Identify the Basic load balancer to upgrade. 
+1. Identify the Basic Load Balancer to upgrade. 
 1. Create a migration plan for planned downtime. 
 1. Perform migration with [automated PowerShell scripts](#upgrade-using-automated-scripts) for your scenario or create a new Standard Load Balancer with the Basic Load Balancer configurations.
-1. Verify your application and workloads are receiving traffic through the standard load balancer. Then delete your basic load balancer resource. 
+1. Verify your application and workloads are receiving traffic through the Standard Load Balancer. Then delete your Basic Load Balancer resource. 
 
 ## Basic Load Balancer SKU vs. Standard Load Balancer SKU 
 
@@ -49,6 +49,8 @@ This section lists out some key differences between these two Load Balancer SKUs
 | **[Private Link Support](../private-link/private-link-overview.md)** | Standard ILB is supported via Private Link | Not supported |
 | **[Global tier (Preview)](cross-region-overview.md)** | Standard Load Balancer supports the Global tier for Public LBs enabling cross-region load balancing | Not supported |
 
+For information on limits, see [Load Balancer limits](../azure-resource-manager/management/azure-subscription-service-limits.md#load-balancer).
+
 ## Upgrade using automated scripts 
 
 Use these PowerShell scripts to help with upgrading from Basic to Standard SKU:

articles/virtual-network/ip-services/public-ip-basic-upgrade-guidance.md

@@ -1,47 +1,46 @@
 ---
 
-title: Upgrading a Basic Public IP to Standard Public IP - Guidance
-description: Overview of upgrade options and guidance for migrating basic Public IP to standard Public IP for future basic Public IP address retirement
+title: Upgrading a Basic public IP address to Standard SKU - Guidance
+description: Overview of upgrade options and guidance for migrating basic public IP to standard public IP for future basic public IP address retirement
 author: mbender-ms
 ms.service: load-balancer
 ms.author: mbender
 ms.topic: overview
 ms.date: 09/19/2022
-#customer-intent: As an cloud engineer with basic Public IP services, I need guidance and direction on migrating my workloads off basic to standard SKUs
+#customer-intent: As an cloud engineer with Basic public IP services, I need guidance and direction on migrating my workloads off basic to Standard SKUs
 ---
 
-# Upgrading a Basic Public IP to Standard Public IP - Guidance
+# Upgrading a Basic public IP address to Standard SKU - Guidance
 
-In this article, we'll discuss guidance for upgrading your Basic Public IPs to Standard Public IPs. Standard Public IPs are recommended for all production instances and provide many [key differences](#basic-sku-vs-standard-sku) to your infrastructure.
+In this article, we'll discuss guidance for upgrading your Basic SKU public IPs to Standard SKU. Standard public IPs are recommended for all production instances and provide many [key differences](#basic-sku-vs-standard-sku) to your infrastructure.
 ## Steps to complete the upgrade 
 
-We recommend the following approach to upgrade to Standard SKU Public IP addresses. 
+We recommend the following approach to upgrade to Standard SKU public IP addresses. 
 
-1. Learn about some of the [key differences](#basic-sku-vs-standard-sku) between Basic Public IP and Standard Public IP. 
-1. Identify the basic public IP to upgrade.
-1. Determine if you would need Zone Redundancy. 
-    1. If you need a zone redundant public IP address, create a new Standard Public IP address using [Portal](create-public-ip-portal.md), [PowerShell](create-public-ip-powershell.md), [CLI](create-public-ip-cli.md), or [ARM template](create-public-ip-template.md).
+1. Learn about some of the [key differences](#basic-sku-vs-standard-sku) between Basic SKU public IP and Standard SKU public IP. 
+1. Identify the Basic SKU public IP to upgrade.
+1. Determine if you would need [Zone Redundancy](public-ip-addresses.md#availability-zone). 
+    1. If you need a zone redundant public IP address, create a new Standard SKU public IP address using [Portal](create-public-ip-portal.md), [PowerShell](create-public-ip-powershell.md), [CLI](create-public-ip-cli.md), or [ARM template](create-public-ip-template.md).
     1. If you do not need a zone redundant public IP address, use the [following upgrade options](#upgrade-using-portal-powershell-and-azure-cli). 
 1. Create a migration plan for planned downtime.
-1. Depending on the resource associated with your Basic Public IP addresses, perform the upgrade based on the following table:
+1. Depending on the resource associated with your Basic SKU public IP addresses, perform the upgrade based on the following table:
 
-    | Resource using Basic Public IP addresses | Decision path |
+    | Resource using Basic SKU public IP addresses | Decision path |
     | ------ | ------ |
     | Virtual Machine or Virtual Machine Scale Sets | use the [following upgrade options](#upgrade-using-portal-powershell-and-azure-cli). |
     | Load Balancer (Basic) | use the [following upgrade options](#upgrade-using-portal-powershell-and-azure-cli).   |
     | VPN Gateway (Basic) | Cannot dissociate and upgrade. Create a [new VPN gateway with a SKU type other than Basic](../../vpn-gateway/tutorial-create-gateway-portal.md). |
     | Application Gateway (v1) | Cannot dissociate and upgrade. Use this [migration script to migrate from v1 to v2](../../application-gateway/migrate-v1-v2.md).  |
-1. Verify your application and workloads are receiving traffic through the Standard Public IP address. Then delete your Basic Public IP address resource. 
+1. Verify your application and workloads are receiving traffic through the Standard SKU public IP address. Then delete your Basic SKU public IP address resource. 
 
 ## Basic SKU vs. Standard SKU 
 
-This section lists out some key differences between these two Public IP addresses SKUs.
+This section lists out some key differences between these two SKUs.
 
-|""| Standard Public IP SKU | Basic Public IP SKU |
+|""| Standard SKU public IP | Basic SKU public IP |
 |---------|---------|---------|
-| **Idle Timeout** | Have an adjustable inbound originated flow idle timeout of 4-30 minutes, with a default of 4 minutes, and fixed outbound originated flow idle timeout of 4 minutes. | Have an adjustable inbound originated flow idle timeout of 4-30 minutes, with a default of 4 minutes, and fixed outbound originated flow idle timeout of 4 minutes. |
 | **Allocation method** | Static. | For IPv4: Dynamic or Static; For IPv6: Dynamic. |
-| **Security** | Secure by default model and be closed to inbound traffic when used as a frontend. Allow traffic with [network security group](../network-security-groups-overview.md#network-security-groups) is required (for example, on the NIC of a virtual machine with a Standard SKU Public IP attached). | Open by default. Network security groups are recommended but optional for restricting inbound or outbound traffic. |
+| **Security** | Secure by default model and be closed to inbound traffic when used as a frontend. Allow traffic with [network security group](../network-security-groups-overview.md#network-security-groups) is required (for example, on the NIC of a virtual machine with a Standard SKU public IP attached). | Open by default. Network security groups are recommended but optional for restricting inbound or outbound traffic. |
 | **[Availability zones](../../availability-zones/az-overview.md)** | Supported. Standard IPs can be non-zonal, zonal, or zone-redundant. Zone redundant IPs can only be created in [regions where three availability zones](../../availability-zones/az-region.md) are live. IPs created before zones are live won't be zone redundant. | Not supported |
 | **[Routing preference](routing-preference-overview.md)** | Supported to enable more granular control of how traffic is routed between Azure and the Internet. | Not supported. |
 | **Global tier** | Supported via [cross-region load balancers](../../load-balancer/cross-region-overview.md)| Not supported |
@@ -59,7 +58,7 @@ Use the Azure portal, Azure PowerShell, or Azure CLI to help upgrade from Basic
 
 ## Next Steps
 
-For guidance on upgrading basic Load Balancer to Standard SKUs, see:
+For guidance on upgrading Basic Load Balancer to Standard SKUs, see:
 
 > [!div class="nextstepaction"]
 > [Upgrading from Basic Load Balancer - Guidance](../../load-balancer/load-balancer-basic-upgrade-guidance.md)