Skip to content

Commit 79475cf

Browse files
committed
Fix review recos
1 parent db200c2 commit 79475cf

File tree

5 files changed

+4
-4
lines changed

5 files changed

+4
-4
lines changed

articles/expressroute/TOC.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@
7070
items:
7171
- name: Private Peering
7272
href: designing-for-disaster-recovery-with-expressroute-privatepeering.md
73-
- name: Using VPN as a Backup
73+
- name: Using VPN as a backup
7474
href: using-s2s-vpn-as-a-backup-for-expressroute-privatepeering.md
7575
- name: How-to guides
7676
items:
43 KB
Loading

articles/expressroute/using-s2s-vpn-as-a-backup-for-expressroute-privatepeering.md renamed to articles/expressroute/use-s2s-vpn-as-backup-for-expressroute-privatepeering.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Unlike geo-redundant ExpressRoute circuits, you can use ExpressRoute-VPN disaste
2323
2424
In this article, let's see how to verify the connectivity both from the Azure perspective and the customer side network edge perspective. Ability to validate from either end will help irrespective of whether or not you manage the customer side network devices that peer with the Microsoft network entities.
2525

26-
## Example Topology
26+
## Example topology
2727

2828
In our setup, we have an on-premises network connected to an Azure hub VNet via both an ExpressRoute circuit and a S2S VPN connection. The Azure hub VNet is in turn peered to a spoke VNet, as shown in the diagram below:
2929

@@ -285,8 +285,8 @@ To enable monitoring and alerts based on VPN gateway metrics, see [Set up alerts
285285
To expedite BGP convergence following an ExpressRoute failure, [Configure BFD over ExpressRoute][BFD].
286286

287287
<!--Image References-->
288-
[1]: ./media/using-s2s-vpn-as-a-backup-for-expressroute-privatepeering/topology.png "topology under consideration"
289-
[2]: ./media/using-s2s-vpn-as-a-backup-for-expressroute-privatepeering/vpn-gw-config.png "VPN GW configuration"
288+
[1]: ./media/use-s2s-vpn-as-backup-for-expressroute-privatepeering/topology.png "topology under consideration"
289+
[2]: ./media/use-s2s-vpn-as-backup-for-expressroute-privatepeering/vpn-gw-config.png "VPN GW configuration"
290290

291291
<!--Link References-->
292292
[DR-PP]: https://docs.microsoft.com/azure/expressroute/designing-for-disaster-recovery-with-expressroute-privatepeering

0 commit comments

Comments
 (0)