Update index.md (cloudflare#2430)

Author: kkrum

products/cloudflare-one/src/content/connections/connect-devices/warp/exclude-traffic/index.md

@@ -32,9 +32,11 @@ Traffic excluded from WARP by Split Tunnel configuration will not be encrypted,
 
 ## Use WARP alongside a VPN
 
-You may still be required to run WARP alongside a legacy VPN product, and we're working to make this experience as seamless as possible. When running in this configuration, there are two important considerations with your deployment:
+You may still be required to run WARP alongside a legacy VPN product, and we're working to make this experience as seamless as possible. When running in this configuration, there are a few important considerations with your deployment:
 
 * **Start WARP first**. WARP and your legacy VPN are both trying to route traffic and DNS requests over our respective networks. Some legacy VPN clients must be the last client to touch a network configuration or they will fail.
 
 * **Turn on Split Tunnel and DNS Fallback in your legacy VPN configuration**. Your legacy VPN may try to route all network traffic and DNS requests through their product by default. For Gateway to function properly, the legacy VPN configuration needs to be set up to only handle the network traffic required for your LOB applications that still require the legacy VPN. All other traffic should fall back to the local machine, so it can be picked up by WARP and protected by Gateway.
+
+* **Split Tunnel your VPN Server**. Make sure the VPN server you are connecting to is also excluded from WARP.