Merge pull request #300761 from MekaylaMoore/patch-31

Update expressroute-howto-gateway-migration-portal.md

Author: v-shils

articles/expressroute/expressroute-howto-gateway-migration-portal.md

@@ -21,7 +21,7 @@ When creating an ExpressRoute virtual network gateway, you must select a [gatewa
 - Ensure you have an existing [ExpressRoute virtual network gateway](expressroute-howto-add-gateway-portal-resource-manager.md) in your Azure subscription.
 
 > [!TIP]
-> You can now deploy two ExpressRoute gateways within the same virtual network. To do this, create a second ExpressRoute gateway with its admin state set to **disabled**. Once the second gateway is deployed, initiate the *Prepare* step in the migration tool. This step will establish the connection without redeploying the gateway, as it is already in place. Finally, run the *Migrate* step, which will change the new gateway's admin state to **_enabled_**, completing the migration process. This method minimizes the migration or maintenance window, significantly reducing downtime when transitioning from a non-zonal to a zone-redundant gateway.
+> You can now deploy two ExpressRoute gateways within the same virtual network. To do this, create a second ExpressRoute gateway with its admin state set to **disabled**. Once the second gateway is deployed, initiate the *Prepare* step in the migration tool. This step establishes the connection without redeploying the gateway, as it's already in place. Finally, run the *Migrate* step, which will change the new gateway's admin state to **_enabled_**, completing the migration process. This method minimizes the migration or maintenance window, significantly reducing downtime when transitioning from a non-zonal to a zone-redundant gateway.
 
 ## Steps to migrate to a new gateway in Azure portal
 
@@ -50,11 +50,11 @@ Follow these steps to migrate to a new gateway using the Azure portal:
 
 1. Select **Prepare** to create the new gateway. This operation can take up to 45 minutes.
 
-1. After the new gateway is created, proceed to the **Migrate** stage. Select the new gateway (for example, **myERGateway_migrated**) to transfer settings from the old gateway to the new one. All network traffic and data path connections transfer without interruptions. Select **Migrate Traffic** to start the process. This step can take up to 5 minutes.
+1. After the new gateway is created, proceed to the **Migrate** stage. Select the new gateway (for example, **myERGateway_migrated**) to transfer settings from the old gateway to the new one. All network traffic and data path connections transfer. Select **Migrate Traffic** to start the process. This step can take up to 5 minutes.
 
     :::image type="content" source="media/gateway-migration/migrate-traffic-step.png" alt-text="Screenshot of migrating traffic for migrating a virtual network gateway." lightbox="media/gateway-migration/migrate-traffic-step.png":::
 
-1. Once traffic migration is complete, proceed to the **Commit** stage. Finalize the migration by deleting the old gateway. Select **Commit Migration** to complete this step without downtime.
+1. Once traffic migration is complete, proceed to the **Commit** stage. Finalize the migration by deleting the old gateway. Select **Commit Migration** to complete this step.
 
     :::image type="content" source="media/gateway-migration/commit-step.png" alt-text="Screenshot of the commit step for migrating a virtual network gateway." lightbox="media/gateway-migration/commit-step.png":::