Update src/content/partials/network-interconnect/bgp-peering.mdx

Co-authored-by: Jun Lee <[email protected]>

Author: marciocloudflare

src/content/partials/network-interconnect/bgp-peering.mdx

@@ -55,7 +55,7 @@ When BGP and static routes have the same prefix and priority, Cloudflare enforce
 
 When BGP advertises a route, it is automatically added to the Magic routing table with a default priority of `100` which <a href={props.configStaticRoutes}>applies to all regions</a>. However, if a static route exists with the same prefix and priority, the static route will always take precedence over the BGP route. You will have to set a different priority for static routes, to be more or less than `100`, depending on which you want to prioritize. Lower values have greater priority.
 
-Additionally, when multiple BGP routes exist with the same prefix length and priority, traffic is distributed across them using <a href={props.ecmp}>equal-cost multi-ath (ECMP) routing</a>.
+Additionally, when multiple BGP routes exist with the same prefix length and priority, traffic is distributed across them using <a href={props.ecmp}>equal-cost multi-path (ECMP) routing</a>.
 
 ## BGP timers and settings