revised photos

Author: MekaylaMoore

articles/expressroute/expressroute-howto-add-gateway-portal-resource-manager.md

@@ -126,11 +126,11 @@ These steps will need to be completed on all virtual networks that need to commu
     You can upgrade:
     * From one Non-Az-enabled SKU to another Non-Az-enabled SKU
 
-     :::image type="content" source="./media/expressroute-howto-add-gateway-portal-resource-manager/standard-sku-upgrade.png" alt-text="Screenshot that shows where to upgrade Gateway SKU for Non-Az Gateways.":::
+        [![Screenshot that shows where to upgrade Gateway SKU for Non-Az Gateways.](./media/expressroute-howto-add-gateway-portal-resource-manager/non-az-upgrade.png)](./media/expressroute-howto-add-gateway-portal-resource-manager/non-az-upgrade.png)
 
     * From one Az-enabled SKU to another Az-enabled SKU
 
-      :::image type="content" source="./media/expressroute-howto-add-gateway-portal-resource-manager/az-sku-upgrade.png" alt-text="Screenshot that shows where to upgrade Gateway SKU for Az Gateways.":::
+        [![Screenshot that shows where to upgrade Gateway SKU for Az Gateways.](./media/expressroute-howto-add-gateway-portal-resource-manager/az-enabled-upgrade.png)](./media/expressroute-howto-add-gateway-portal-resource-manager/az-enabled-upgrade.png)
 
 
 For all other downgrade scenarios, you need to delete and re-create the gateway, which incurs downtime.

articles/expressroute/gateway-migration.md

@@ -48,7 +48,10 @@ For enhanced reliability and high availability, we recommend migrating to an Az-
 
 1. **Validate**: Check that all resources are in a succeeded state. If any prerequisites aren't met, validation fails and migration can't proceed.
 2. **Prepare**: Azure creates a new virtual network gateway, public IP, and connections. This step can take up to 45 minutes. You can specify a name for the new gateway, or Azure will add **_migrated** to the original name by default. During preparation, the existing gateway is locked to prevent changes. If you need to stop the migration, you can **abort** at this stage, which deletes the new gateway and connections.
-    - **Note**: The new gateway is created in the same region as the existing one. To change regions, you must delete the current gateway and create a new one in the desired region.
+
+> [!NOTE]
+> The new gateway is created in the same region as the existing one. To change regions, you must delete the current gateway and create a new one in the desired region.
+
 3. **Migrate**: Switch traffic from the old gateway to the new one. This step can take up to 15 minutes and may cause brief connectivity interruptions.
 4. **Commit**: Complete the migration by deleting the old gateway and its connections. If necessary, you can abort and revert to the old gateway before committing.