broken link fix

Author: erjosito

articles/route-server/anycast.md

@@ -21,7 +21,7 @@ IP anycast essentially consists of advertising exactly the same IP address from
 
 In the design covered in this scenario, the same IP address will be advertised from VNets in different Azure regions, where NVAs will advertise the application's IP address through Azure Route Server. The following diagram depicts two simple hub and spoke topologies, each in a different Azure region. A Network Virtual Appliance (NVA) in each region advertises the same route (`a.b.c.d/32` in this example, it could be any prefix that ideally does not overlap with the Azure and on-premises networks) to its local Azure Route Server. The routes will be further propagated to the on-premises network through ExpressRoute. When application users want to access the application from on-premises, the DNS infrastructure (not covered by this document) will resolve the DNS name of the application to the anycast IP address (`a.b.c.d` in the diagram), which the on-premises network devices will route to one of the two regions.
 
-:::image type="content" source="media/senarios/anycast.png" alt-text="Diagram of anycast with Route Server.":::
+:::image type="content" source="media/scenarios/anycast.png" alt-text="Diagram of anycast with Route Server.":::
 
 The decision of which of the available regions is selected is entirely based on routing attributes. If the routes from both regions are identical, the on-premises network will typically use Equal Cost MultiPathing (ECMP) to send each application flow to each region. It is possible as well to modify the advertisements generated by each NVA in Azure to make one of the regions preferred, for example with BGP AS Path prepending, establishing a deterministic path from on-premises to the azure workload..