adjusted subheaders

Author: marciocloudflare

src/content/partials/networking-services/routing/bgp-peering.mdx

@@ -57,11 +57,11 @@ When BGP advertises a route, it is automatically added to the Magic routing tabl
 
 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>.
 
-### Change route priorities with BGP attributes
+## Change route priorities with BGP attributes
 
 Cloudflare supports traffic engineering via BGP communities and AS prepending. You can use these traffic routing techniques to set route priorities and perform traffic engineering across multiple interconnects.
 
-#### BGP communities for setting route priority
+### BGP communities for setting route priority
 
 The default BGP route priority is `100`. This base priority can be adjusted using communities. For example, when a route is tagged with the community `13335:60010` its priority is set to `10`. This makes it a higher priority than the default of `100` because lower numeric priorities are preferred.
 
@@ -77,7 +77,7 @@ The community values supported for setting base route priority are:
 
 It is considered a misconfiguration to set multiple base priority communities in the same prefix update message. In this situation the highest priority (lowest integer value) is preferred.
 
-#### AS path prepending for adjusting route priority
+### AS path prepending for adjusting route priority
 
 For each additional mention of the customer ASN in the received AS path an additional `10` is added to the route's base priority. By increasing the priority number, the route is less preferred.
 
@@ -94,7 +94,7 @@ AS_PATH: 65000 65000 65200
 AS_PATH: 65000 65000 65200
 ```
 
-#### How communities and prepends work together
+### How communities and prepends work together
 
 Cloudflare adjusts route priority when using AS prepending with communities. For example, if a route is tagged with `13335:60150`, the base priority is set to `150`. If you prepend your ASN twice, Cloudflare adds `10` for each prepend, increasing the route priority to `180`.