refined code

Author: marciocloudflare

src/content/docs/magic-transit/how-to/bgp-peering.mdx

@@ -13,6 +13,6 @@ import { Render } from "~/components"
 	params={{
 		productName: "Magic Transit",
 		productPath: "/magic-transit/reference/tunnel-health-checks/",
-		legacyHCs: "/magic-transit/reference/tunnel-health-checks/#legacy-health-checks-system"
+		legacyHCs: "/magic-transit/reference/tunnel-health-checks/#legacy-health-checks-system",
 	}}
 />

src/content/docs/magic-wan/configuration/manually/how-to/bgp-peering.mdx

@@ -13,6 +13,6 @@ import { Render } from "~/components"
 	params={{
 		productName: "Magic WAN",
 		productPath: "/magic-wan/reference/tunnel-health-checks/",
-		legacyHCs: "/magic-wan/reference/tunnel-health-checks/#legacy-health-checks-system"
+		legacyHCs: "/magic-wan/reference/tunnel-health-checks/#legacy-health-checks-system",
 	}}
 />

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

@@ -22,7 +22,7 @@ With this functionality, customers can:
 
 Routes received from the customer device will be redistributed into the Magic routing table, which is used by both Magic WAN and Magic Transit.
 
-All routes in the Magic routing table are advertised to BGP peers. Each BGP peer will receive each prefix route along with the full `AS_PATH`, with the selected Cloudflare side ASN prepended. This is so that the peer can accurately perform loop prevention.
+All routes in the Magic routing table are advertised to BGP peers. Each BGP peer will receive each prefix route along with the full `AS_PATH`, with the selected Cloudflare side ASN prepended. This is so that the peer can accurately perform [loop prevention](https://datatracker.ietf.org/doc/html/rfc4271#section-9.1.2).
 
 BGP peering sessions can advertise reachable prefixes to a peer and withdraw previously advertised prefixes. This should not take more than a few minutes to propagate.
 
@@ -60,7 +60,6 @@ By default each BGP peering session will use the same Cloudflare side ASN to rep
 - The Cloudflare side ASN will never be exposed in `AS PATH` of anycast announcements from the Cloudflare edge. In those announcements, Cloudflare will always use the Cloudflare ASN of `13335` optionally prepended with a bring-your-own ASN as described in [Cloudflare ASN vs. your own ASN](/magic-transit/how-to/advertise-prefixes/#cloudflare-asn-vs-your-own-asn)
 - The customer device ASN can be a private ASN, or the ASN they are using for Magic Transit anycast announcements at the edge: this has no impact on the ASN for the Anycast announced prefix at the edge of the Cloudflare global network.
 
-
 ## How to set up BGP peering
 
 :::caution