Merge pull request #306458 from raboilla/patch-33

VPN Gateway keyword add-Update article title for VPN Gateway migration

Author: prmerger-automator[bot]

articles/vpn-gateway/basic-public-ip-migrate-howto.md

@@ -1,5 +1,5 @@
 ---
-title: How to migrate a Basic SKU public IP address to a Standard SKU - Preview
+title: How to migrate a Basic SKU public IP address to a Standard SKU for VPN Gateway - Preview
 titleSuffix: Azure VPN Gateway
 description: Learn how to migrate from a Basic SKU public IP address to a Standard SKU public IP address for VPN Gateway deployment.
 author: cherylmc
@@ -10,7 +10,7 @@ ms.author: cherylmc
 # Customer intent: As a cloud network administrator, I want to migrate a Basic SKU public IP address to a Standard SKU for VPN Gateway, so that I can ensure optimal performance and compliance with service standards during our infrastructure upgrade.
 ---
 
-# How to migrate a Basic SKU public IP address to Standard SKU - Preview
+# How to migrate a Basic SKU public IP address to Standard SKU for VPN Gateway - Preview
 
 This article helps you migrate a Basic SKU public IP address to a Standard SKU for VPN Gateway deployments that use gateway SKUs VpnGw 1-5 for active-passive gateways (not active-active). For more information about Basic SKU migration, see [About migrating a Basic SKU public IP address to Standard SKU for VPN Gateway](basic-public-ip-migrate-about.md).
 
@@ -35,7 +35,7 @@ In the Azure portal, there are three sections for the migration process:
   * Migrate the VPN Gateway gateway SKU from a non-AZ SKU to an AZ SKU. For example, VpnGw2 becomes VpnGw2AZ.
 * The third section validates the migration and deletes the old Basic SKU public IP address resource.
 
-## <a name="migrate"></a>Migrate to a Standard SKU public IP address
+## <a name="migrate"></a>Migrate to a Standard SKU public IP address for VPN Gateway
 
 #### [Portal](#tab/portal)