fixed errors.

Author: AbdullahBell

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

@@ -40,7 +40,7 @@ We recommend the following approach to upgrade to Standard SKU public IP address
   | Virtual Machine | Use scripts or manually detach and upgrade public IPs. For standalone virtual machines, you can use the [upgrade script](public-ip-upgrade-vm.md) or for virtual machines in an availability set use [this script](public-ip-upgrade-availability-set.md). |
   | Virtual Machine Scale Sets | [Replace basic SKU instance public IP addresses](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-networking#public-ipv4-per-virtual-machine) with new standard SKU |
   | Load Balancer (Basic SKU) | New Load Balancer SKU required. Use the upgrade script [Upgrade Basic Load Balancer to Standard SKU](../../load-balancer/upgrade-basic-standard-with-powershell.md) to upgrade to Standard Load Balancer |
-  | VPN Gateway (using Basic IPs) | A migration path will be provided in the future. When this migration path is available, we'll update this decision path with migration information and send out a service health alert. For more information, see [Migrating a basic SKU FAQ](../../vpn-gateway/vpn-gateway-vpn-faq#migrating-a-basic-sku-public-ip-address-to-standard-sku) |
+  | VPN Gateway (using Basic IPs) | A migration path will be provided in the future. When this migration path is available, we'll update this decision path with migration information and send out a service health alert. For more information, see [Migrating a basic SKU FAQ](../vpn-gateway/vpn-gateway-vpn-faq#migrating-a-basic-sku-public-ip-address-to-standard-sku) |
   |  ExpressRoute Gateway (using Basic IPs) | New ExpressRoute Gateway is required. Follow the [ExpressRoute Gateway migration guidance](../../expressroute/gateway-migration.md) for upgrading from Basic to Standard SKU.  |
   | Application Gateway (v1 SKU) | New AppGW SKU required. Use this [migration script to migrate from v1 to v2](../../application-gateway/migrate-v1-v2.md).  |
 

articles/vpn-gateway/vpn-gateway-vpn-faq.md

@@ -211,11 +211,11 @@ The Standard and High Performance SKUs will be deprecated on September 30, 2025.
 
 ## Migrating a Basic SKU public IP address to Standard SKU
 
-This section outlines important questions and considerations for migrating from a Basic SKU public IP address to a Standard SKU public IP address for VPN Gateway deployments currently using a Basic SKU public IP address. This does not pertain to deployments that are already using a Standard SKU public IP address. For more information, see [Basic SKU IP deprecation Announcement](https://azure.microsoft.com/en-us/updates?id=upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired.
+This section outlines important questions and considerations for migrating from a Basic SKU public IP address to a Standard SKU public IP address for VPN Gateway deployments currently using a Basic SKU public IP address. This does not pertain to deployments that are already using a Standard SKU public IP address. For more information, see [Basic SKU IP deprecation Announcement](https://azure.microsoft.com/updates?id=upgrade-to-standard-sku-public-ip-addresses-in-azure-by-30-september-2025-basic-sku-will-be-retired).
 
 ### What is the expected customer impact?
 
-The expected customer impact includes new [pricing](https://azure.microsoft.com/en-us/pricing/details/ip-addresses/) changes and up to 10 minutes of downtime during customer-controlled migration. Customers will have three months to migrate after the release of the migration tool. To qualify for a successful migration, ensure you have the correct IP address space and subnet size.
+The expected customer impact includes new [pricing](https://azure.microsoft.com/pricing/details/ip-addresses/) changes and up to 10 minutes of downtime during customer-controlled migration. Customers will have three months to migrate after the release of the migration tool. To qualify for a successful migration, ensure you have the correct IP address space and subnet size.
 
 ### What is the anticipated timeline for the migration?