update

Author: deadlypants1973

src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains.mdx

@@ -52,5 +52,5 @@ The domain will no longer be excluded from Gateway DNS policies, effective immed
 ## Related resources
 
 - [Connectivity status](/cloudflare-one/connections/connect-devices/warp/troubleshooting/connectivity-status/) - Learn about the status messages displayed by the WARP client during its connection process, and understand each stage as WARP establishes a secure tunnel to Cloudflare.
-- [Local Domain Fallback](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains/) - Resolve selected domains via local DNS instead of Cloudflare Gateway.
+- [Split Tunnels](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/) - Control which traffic goes through WARP by including or excluding specific IPs or domains.
 - [WARP with firewall](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/) - Learn which IPs, domains, and ports to allow so users can deploy and connect WARP successfully behind a firewall.

src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels.mdx

@@ -104,5 +104,5 @@ If you need to revert to the default Split Tunnel entries recommended by Cloudfl
 ## Related resources
 
 - [Connectivity status](/cloudflare-one/connections/connect-devices/warp/troubleshooting/connectivity-status/) - Learn about the status messages displayed by the WARP client during its connection process, and understand each stage as WARP establishes a secure tunnel to Cloudflare.
-- [Split Tunnels](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/split-tunnels/) - Control which traffic goes through WARP by including or excluding specific IPs or domains.
+- [Local Domain Fallback](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/local-domains/) - Resolve selected domains via local DNS instead of Cloudflare Gateway.
 - [WARP with firewall](/cloudflare-one/connections/connect-devices/warp/deployment/firewall/) - Learn which IPs, domains, and ports to allow so users can deploy and connect WARP successfully behind a firewall.

src/content/docs/cloudflare-one/connections/connect-devices/warp/configure-warp/warp-settings/captive-portals.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 3
 ---
 
-import { Details, Badge } from "~/components";
+import { Details, Badge, Render } from "~/components";
 
 Captive portals are used by public Wi-Fi networks (such as airports, coffee shops, and hotels) to make a user agree to their Terms of Service or provide payment before allowing access to the Internet. When a user connects to the Wi-Fi, the captive portal blocks all HTTPS traffic until the user completes a captive portal login flow in their browser. This prevents the WARP client from connecting to Cloudflare. At the same time, WARP creates [firewall rules](/cloudflare-one/connections/connect-devices/warp/configure-warp/route-traffic/warp-architecture/#ip-traffic) on the device to send all traffic to Cloudflare. The user is therefore unable to access the captive portal login screen unless they temporarily disable WARP.
 

src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/fleet.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 import { Render } from "~/components";
 
-This guide covers how to deploy the Cloudflare WARP client using [Fleet](https://fleetdm.com/) device management software. {}
+This guide covers how to deploy the Cloudflare WARP client using [Fleet](https://fleetdm.com/) device management software.
 
 ## macOS
 
@@ -22,7 +22,9 @@ This guide covers how to deploy the Cloudflare WARP client using [Fleet](https:/
 2. From the **Teams** dropdown, select the team (group of hosts) that requires Cloudflare WARP.
 3. Select **OS settings** > **Custom settings**.
 4. Select **Add profile** and upload the custom `.mobileconfig`.
-5. Select the hosts which require Cloudflare WARP: - **All hosts**: Deploys WARP to all hosts in the team. - **Custom**: Deploys WARP to a subset of the hosts in the team. Use [labels](https://fleetdm.com/guides/managing-labels-in-fleet#basic-article) to define the hosts that should be included or excluded.
+5. Select the hosts which require Cloudflare WARP:
+   - **All hosts**: Deploys WARP to all hosts in the team.
+   - **Custom**: Deploys WARP to a subset of the hosts in the team. Use [labels](https://fleetdm.com/guides/managing-labels-in-fleet#basic-article) to define the hosts that should be included or excluded.
 6. Select **Add profile**.
 
 The defined hosts will immediately receive the deployment profile, but WARP is not yet installed.

src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/hexnode.mdx

@@ -8,8 +8,6 @@ description: Deploy Cloudflare WARP with Hexnode MDM - Step-by-step guide for Wi
 
 import { Render } from "~/components";
 
-<Render file="warp/connectivity-status-check" />
-
 ## Windows
 
 1. Create a script file with `.bat`, `.cmd`, and `.ps1` file formats to download, install and configure the Cloudflare WARP client Windows application on the device. Listed below is a sample script with all of the configurable parameters:
@@ -50,6 +48,8 @@ import { Render } from "~/components";
 
 7. Select **Execute**.
 
+<Render file="warp/connectivity-status-check" />
+
 ## macOS
 
 1. [Download](/cloudflare-one/connections/connect-devices/warp/download-warp/#macos) the Cloudflare WARP client for macOS.
@@ -100,6 +100,8 @@ import { Render } from "~/components";
 
 This will push the app along with the configurations to the selected devices.
 
+<Render file="warp/connectivity-status-check" />
+
 ## iOS
 
 1. On your Hexnode console, go to **Apps** > **Add Apps** > **Store App**.
@@ -142,6 +144,8 @@ This will push the app along with the configurations to the selected devices.
 
 This will push the app along with the configurations to the selected devices.
 
+<Render file="warp/connectivity-status-check" />
+
 ## Android
 
 1. On your Hexnode console, go to **Apps** > **Add Apps** > **Managed Google Apps**.
@@ -154,3 +158,5 @@ This will push the app along with the configurations to the selected devices.
 8. Save the policy.
 
 This will push the app along with the configurations to the selected devices.
+
+<Render file="warp/connectivity-status-check" />

src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/index.mdx

@@ -8,7 +8,7 @@ head:
     content: Deploy WARP with Technology Partners
 ---
 
-import { DirectoryListing, Render } from "~/components";
+import { DirectoryListing } from "~/components";
 
 Cloudflare Zero Trust integrates with [Cloudflare Technology Partner](https://www.cloudflare.com/partners/technology-partners/) tools to help you deploy the WARP client to bigger fleets of devices. Thanks to these collaborations, you can distribute the WARP client application to end-user devices and remotely set up advanced configurations in real time.
 

src/content/docs/cloudflare-one/connections/connect-devices/warp/deployment/mdm-deployment/partners/kandji.mdx

@@ -58,6 +58,8 @@ For the simplest deployment, Kandji has created a downloadable configuration pro
 
 To verify that Cloudflare WARP was installed, select the app in the **Custom App** library and view its **Status** tab.
 
+<Render file="warp/connectivity-status-check" />
+
 ## Audit and Enforce Script
 
 The following audit script checks if the WARP client is installed and optionally enforces a minimum version number.