Update warp-to-warp.mdx - Split tunnel Exclude mode (#18609)

* Update warp-to-warp.mdx - Split tunnel Exclude mode

Instead of simply excluding 100.96.0.0/12 from split tunneling in Exclude mode, this removes only the CGNAT IP range that CloudFlare WARP need. Info taken from another page on the CloudFlare documentation.

https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/private-net/warp-connector/user-to-site/#3-route-cgnat-ips-through-cloudflare

* Update warp-to-warp.mdx

---------

Co-authored-by: ranbel <[email protected]>

Author: Doneven2012

src/content/docs/cloudflare-one/connections/connect-networks/private-net/warp-to-warp.mdx

@@ -34,7 +34,7 @@ This guide covers how to:
 3. Enable **Warp-to-Warp**. This allows Cloudflare to route traffic to the <GlossaryTooltip term="CGNAT IP">CGNAT IP</GlossaryTooltip> space.
 4. In your [Split Tunnel configuration](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/), ensure that traffic to `100.96.0.0/12` is going through WARP:
 
-- If using **Exclude** mode, remove `100.96.0.0/12` from your list.
+- If using **Exclude** mode, delete `100.64.0.0/10` from the list and re-add `100.64.0.0/11` and `100.112.0.0/12`.
 - If using **Include** mode, add `100.96.0.0/12` to your list.
 
 This will instruct WARP to begin proxying any traffic destined for a `100.96.0.0/12` IP address to Cloudflare for routing and policy enforcement.