updated step 8

Author: marciocloudflare

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

@@ -15,6 +15,7 @@ import { Render } from "~/components"
 		productPath: "/magic-transit/reference/tunnel-health-checks/",
 		legacyHCs: "/magic-transit/reference/tunnel-health-checks/#legacy-health-checks-system",
 		asnProduct: "<br /> Magic Transit customers should also be aware of the following: <br /> <ul><li>The Cloudflare side ASN will never be exposed in <code>AS_PATH</code> of anycast announcements from the Cloudflare edge. In those announcements, Cloudflare will always use the Cloudflare ASN of <code>13335</code> 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)</li><li>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.</li></ul>",
-		mtLimitations: "<br /> For Magic Transit customers, BGP with the Magic routing table is separated from the announcement of anycast prefixes at the Cloudflare edge. Anycast withdrawal must be controlled with existing methods documented in [Advertise prefixes](https://developers.cloudflare.com/magic-transit/how-to/advertise-prefixes/)."
+		mtLimitations: "<br /> For Magic Transit customers, BGP with the Magic routing table is separated from the announcement of anycast prefixes at the Cloudflare edge. Anycast withdrawal must be controlled with existing methods documented in [Advertise prefixes](https://developers.cloudflare.com/magic-transit/how-to/advertise-prefixes/).",
+		productGatewayOrEgress: "Magic Transit with Egress"
 	}}
 />

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

@@ -15,6 +15,7 @@ import { Render } from "~/components"
 		productPath: "/magic-wan/reference/tunnel-health-checks/",
 		legacyHCs: "/magic-wan/reference/tunnel-health-checks/#legacy-health-checks-system",
 		asnProduct: "<br /> Magic WAN customers should also be aware of the following: <br /> <ul><li>The Cloudflare side ASN will be included in the <code>AS_PATH</code> of announced routes to any BGP enabled interconnect.</li><li>The customer chooses their device ASN, which should be different to the Cloudflare-side ASN.</li></ul>",
-		mtLimitations: " "
+		mtLimitations: " ",
+		productGatewayOrEgress: "Magic WAN with Gateway"
 	}}
 />

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

@@ -5,6 +5,7 @@ params:
   - legacyHCs
   - asnProduct
   - mtLimitations
+  - productGatewayOrEgress
 ---
 
 import { Markdown } from "~/components";
@@ -91,5 +92,7 @@ If you already have set up your Cloudflare account ASN, you can skip steps two a
 5. Find the Direct CNI interconnect you want to configure with BGP > select the **three dots** next to it > **Configure BGP**.
 6. In **Customer device ASN**, enter the ASN for your network.
 7. In **MD5 key**, you can optionally enter the key for your network. Note that this is meant to prevent accidental misconfigurations, and is not a security mechanism.
-8. (Optional) In **Advertised prefix list**, input the additional static prefixes automatically assigned by Cloudflare during the creation of the CNI interconnect, to advertise alongside your existing routes. Leave blank if you do not want to advertise extra routes.
-9. Select **Enable BGP**.
+8. (Optional) In **Advertised prefix list**, input the additional prefixes automatically assigned by Cloudflare during the creation of the CNI interconnect, to advertise alongside your existing routes. Leave blank if you do not want to advertise extra routes. <br /> Typical prefixes to configure here include:
+	- A route to `0.0.0.0/0`, the default route — to attract all Internet-bound traffic if using {props.productGatewayOrEgress}.
+	- A route to `100.96.0.0/12`, the portion of CGNAT space [used by default with WARP clients](/cloudflare-one/connections/connect-networks/private-net/warp-connector/user-to-site/#add-route-to-router).
+9. Select **Enable BGP**.