Update articles/frontdoor/high-availability.md

Co-authored-by: John Downs <[email protected]>

Author: halkazwini

articles/frontdoor/high-availability.md

@@ -75,7 +75,7 @@ This DNS-based load balancing solution uses multiple Azure Traffic Manager profi
 
 :::image type="content" source="./media/high-availability/front-door-application-gateway.svg" alt-text="Diagram showing Azure Traffic Manager with weighted routing to Azure Front Door, and a nested Traffic Manager profile using performance routing to send to Application Gateway instances in two regions." border="false" lightbox="./media/high-availability/front-door-application-gateway.svg":::
 
-**Traffic flow (Normal operation):** User → DNS Query → Primary Traffic Manager (Weighted / Always server routing) → Front Door (Priority 1) → Origin Servers.
+**Traffic flow (Normal operation):** User → DNS Query → Primary Traffic Manager (Weighted / Always serve routing) → Front Door (Priority 1) → Origin Servers.
 
 **Traffic flow (Front Door failure):** User → DNS Query → Primary Traffic Manager (Weighted / Always server routing) → Secondary Traffic Manager (Priority mode) → Application Gateway(s) → Origin Servers.