Skip to content

Commit aab3d66

Browse files
authored
Fix typos and improve clarity in documentation
1 parent df61897 commit aab3d66

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,9 +68,9 @@ Here are the steps to migrate to a new gateway in Azure portal.
6868

6969

7070
>[!IMPORTANT]
71-
> - Before running this step, verify that the new virtual network gateway has a working ExpressRoute connection and vaildate if the traffic is flowing through the new connection.
71+
> - Before running this step, verify that the new virtual network gateway has a working ExpressRoute connection and validate if the traffic is flowing through the new connection.
7272
> - When migrating your gateway, you can expect possible interruption for a maximum of 30 seconds.
73-
> - Once committed, the connection name cannot be changed and has to be deleted and recreated if one wants to change the connection naming. Please reach out to Azure support in case of any issues.
73+
> - Once committed, the connection name can't be changed and has to be deleted and recreated if you want to change the connection naming. Reach out to Azure support in case of any issues.
7474
7575
## Next steps
7676

0 commit comments

Comments
 (0)