From 97df8b3f6e2594be27ee970e1f7fb6aecf0f5094 Mon Sep 17 00:00:00 2001
From: ricardomacas <157506597+ricardomacas@users.noreply.github.com>
Date: Wed, 15 Jan 2025 14:09:54 +0000
Subject: [PATCH 1/2] Clarifying anycast vs local prefixes

Clarified the difference between anycast prefixes and local prefixes.
---
 .../classic-cni/set-up/configure-bgp-bfd.mdx                    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/docs/network-interconnect/classic-cni/set-up/configure-bgp-bfd.mdx b/src/content/docs/network-interconnect/classic-cni/set-up/configure-bgp-bfd.mdx
index f83630ce0d5cc4..86e110f59ccc84 100644
--- a/src/content/docs/network-interconnect/classic-cni/set-up/configure-bgp-bfd.mdx
+++ b/src/content/docs/network-interconnect/classic-cni/set-up/configure-bgp-bfd.mdx
@@ -36,7 +36,7 @@ If you have a virtual link via Megaport, the IP provisioning may fail if you hav
 
 After you provision the IPs and the ping tests confirm the connection, accept the routes from the BGP session Cloudflare configured. Configuring the BGP session on both the Cloudflare and user sides requires a BGP call and an approximately two hour maintenance window that you provide to Cloudflare.
 
-Cloudflare advertises all of its anycast prefixes including [BYOIP](/byoip/) prefixes over CNI, but the process occurs over a private link from Cloudflare to the customer data center.
+Cloudflare advertises all of its available anycast prefixes including [BYOIP](/byoip/) prefixes over CNI, but this can exclude other location-specific prefixes that may not be available at that datacenter, and the BGP session occurs over a private link from Cloudflare to the customer data center.
 
 :::note
 Your CNI needs to accept all of Cloudflare's prefixes to ensure it is fully utilized, and traffic routed from the data centers back to the CNI is secure, fast, and reliable.

From 15da6ebff749155f64cadcf5bdd74af22ef0a7fb Mon Sep 17 00:00:00 2001
From: marciocloudflare <83226960+marciocloudflare@users.noreply.github.com>
Date: Wed, 15 Jan 2025 14:34:28 +0000
Subject: [PATCH 2/2] Update
 src/content/docs/network-interconnect/classic-cni/set-up/configure-bgp-bfd.mdx

---
 .../classic-cni/set-up/configure-bgp-bfd.mdx                    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/content/docs/network-interconnect/classic-cni/set-up/configure-bgp-bfd.mdx b/src/content/docs/network-interconnect/classic-cni/set-up/configure-bgp-bfd.mdx
index 86e110f59ccc84..6ef59ef9590787 100644
--- a/src/content/docs/network-interconnect/classic-cni/set-up/configure-bgp-bfd.mdx
+++ b/src/content/docs/network-interconnect/classic-cni/set-up/configure-bgp-bfd.mdx
@@ -36,7 +36,7 @@ If you have a virtual link via Megaport, the IP provisioning may fail if you hav
 
 After you provision the IPs and the ping tests confirm the connection, accept the routes from the BGP session Cloudflare configured. Configuring the BGP session on both the Cloudflare and user sides requires a BGP call and an approximately two hour maintenance window that you provide to Cloudflare.
 
-Cloudflare advertises all of its available anycast prefixes including [BYOIP](/byoip/) prefixes over CNI, but this can exclude other location-specific prefixes that may not be available at that datacenter, and the BGP session occurs over a private link from Cloudflare to the customer data center.
+Cloudflare advertises all of its available anycast prefixes, including [BYOIP](/byoip/) prefixes, over a private CNI link between Cloudflare and the customer data center. However, this can exclude other location-specific prefixes that may not be available at that datacenter.
 
 :::note
 Your CNI needs to accept all of Cloudflare's prefixes to ensure it is fully utilized, and traffic routed from the data centers back to the CNI is secure, fast, and reliable.