Update public-ip-basic-upgrade-guidance.md

-------
cc: @mbender-ms

Author: brianlehr

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

@@ -10,7 +10,7 @@ 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
 ---
 
-# Upgrading a basic public IP address to standard SKU - Guidance
+# Upgrading a basic public IP address to Standard SKU - Guidance
 
 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 
@@ -33,7 +33,7 @@ We recommend the following approach to upgrade to Standard SKU public IP address
     | 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 SKU public IP address. Then delete your Basic SKU public IP address resource. 
 
-## Basic SKU vs. standard SKU 
+## Basic SKU vs. Standard SKU 
 
 This section lists out some key differences between these two SKUs.
 
@@ -61,4 +61,4 @@ Use the Azure portal, Azure PowerShell, or Azure CLI to help upgrade from Basic
 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)
+> [Upgrading from Basic Load Balancer - Guidance](../../load-balancer/load-balancer-basic-upgrade-guidance.md)