[ZT] WARP Client --> Cloudflare One Client image audit (#29104)

* WARP Client images

* update mermaid diagrams

Author: ranbel

src/assets/images/reference-architecture/cloudflare-sase-with-crowdstrike/Main_Arch.svg

@@ -14,13 +14,13 @@ Cloudflare One allows you to enforce custom device posture checks on your applic
 
 ```mermaid
 sequenceDiagram
-    participant WARP
+    participant Cloudflare One Client
 		participant Cloudflare Access
     participant External API
-    WARP->>Cloudflare Access: Client ID and Secret
+    Cloudflare One Client->>Cloudflare Access: Client ID and Secret
 		Cloudflare Access->>External API: Application token
-		WARP->>External API: JSON with user and device identity
-    External API-->>WARP: JSON with 0-100 result
+		Cloudflare One Client->>External API: JSON with user and device identity
+    External API-->>Cloudflare One Client: JSON with 0-100 result
 ```
 
 ## External API requirements
@@ -35,14 +35,14 @@ The Cloudflare One Client authenticates to the external API through Cloudflare A
 
 Cloudflare will pass the following parameters to the configured API endpoint. You can use this data to identify the device and assign a posture score. For some devices, not all identifying information will apply, in which case the field will be blank. A maximum of 1,000 devices will be sent per a request.
 
-| Field           | Description                                        |
-| --------------- | -------------------------------------------------- |
+| Field           | Description                                                  |
+| --------------- | ------------------------------------------------------------ |
 | `device_id`     | Device UUID assigned by the Cloudflare One Client            |
 | `email`         | Email address used to authenticate the Cloudflare One Client |
-| `serial_number` | Device serial number                               |
-| `mac_address`   | Device MAC address                                 |
-| `virtual_ipv4`  | Device virtual IPv4 address                        |
-| `hostname`      | Device name                                        |
+| `serial_number` | Device serial number                                         |
+| `mac_address`   | Device MAC address                                           |
+| `virtual_ipv4`  | Device virtual IPv4 address                                  |
+| `hostname`      | Device name                                                  |
 
 :::note
 

src/assets/images/reference-architecture/cloudflare-sase-with-crowdstrike/UseCase01.svg

@@ -15,7 +15,10 @@ Our lightweight and open-source connector, [`cloudflared`](https://github.com/cl
 
 Cloudflare Tunnel allows users to deploy additional instances of our connector, `cloudflared`, for availability and failover scenarios. We refer to these unique instances as replicas. Each replica establishes four new connections which serve as additional points of ingress to your origin, should you need them. Each of the replicas will point to the same tunnel. This ensures that your network remains up in the event a single host running `cloudflared` goes down.
 
-<Render file="tunnel/availability/cloudflared-replicas-diagram" product="cloudflare-one" />
+<Render
+	file="tunnel/availability/cloudflared-replicas-diagram"
+	product="cloudflare-one"
+/>
 
 By design, replicas do not offer any level of traffic steering (random, hash, or round-robin). Instead, when a request arrives to Cloudflare, it will be forwarded to the replica that is geographically closest. If that distance calculation is unsuccessful or the connection fails, we will retry others, but there is no guarantee about which connection is chosen.
 
@@ -36,7 +39,7 @@ graph LR
     accTitle: Load balancing traffic to applications behind Cloudflare Tunnel
 
     A[Internet] --> C{Cloudflare <br> Load Balancer}
-    B[WARP clients] --> C
+    B[Cloudflare One Client] --> C
     M[Cloudflare WAN] --> C
     C -- Tunnel 1 --> cf1
     C -- Tunnel 2 --> cf2
@@ -74,4 +77,4 @@ There are two types of load balancers that you can use with Cloudflare Tunnel en
 
 :::note
 [Private hostname routes](/cloudflare-one/networks/connectors/cloudflare-tunnel/private-net/cloudflared/connect-private-hostname/) are not currently compatible with Load Balancing. If your service is connected via a hostname route, use `cloudflared` [replicas](#cloudflared-replicas) for high availability.
-:::
+:::

src/assets/images/reference-architecture/cloudflare-sase-with-crowdstrike/UseCase02.svg

@@ -21,14 +21,14 @@ This guide covers how to connect Cloudflare One Client user devices to a private
       router1["WARP Connector
         10.0.0.1"]
       end
-      W[WARP clients]-->C((Cloudflare))-->router1
+      W[Cloudflare One Client]-->C((Cloudflare))-->router1
 ```
 
 ## Prerequisites
 
 - A Linux host [^1] on the subnet.
 - For WARP Connector to connect to Cloudflare services, your firewall should allow inbound/outbound traffic for the [WARP IP addresses, ports, and domains](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/deployment/firewall/).
-- For Cloudflare One Clients to connect to your subnet, your firewall should allow inbound traffic from  your [device IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/).
+- For Cloudflare One Clients to connect to your subnet, your firewall should allow inbound traffic from your [device IPs](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/).
 
 ## 1. Install a WARP Connector
 
@@ -43,8 +43,7 @@ This guide covers how to connect Cloudflare One Client user devices to a private
 Cloudflare One Clients and WARP Connectors are accessed using their [device IP](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/device-ips/). Therefore, traffic to your device IPs must route through Cloudflare on both the WARP Connector host and Cloudflare One Client devices.
 
 1. In your WARP Connector device profile, go to [Split Tunnels](/cloudflare-one/team-and-resources/devices/cloudflare-one-client/configure/route-traffic/split-tunnels/).
-2.
-	<Render file="tunnel/cgnat-split-tunnels" product="cloudflare-one" />
+2. <Render file="tunnel/cgnat-split-tunnels" product="cloudflare-one" />
 
 3. Repeat the previous steps for all Cloudflare One Client device profiles.
 
@@ -120,13 +119,11 @@ You can now send a request from a Cloudflare One Client user device to your subn
       router1["WARP Connector
         10.0.0.1"]
       end
-      W[WARP client]--ping 10.0.0.2 -->C((Cloudflare))-->router1
+      W[Cloudflare One Client]--ping 10.0.0.2 -->C((Cloudflare))-->router1
 ```
 
 [^1]:
     <Render
     	file="tunnel/warp-connector-linux-packages"
     	product="cloudflare-one"
     />
-
-

src/assets/images/reference-architecture/cloudflare-sase-with-crowdstrike/UseCase03.svg

@@ -52,7 +52,7 @@ Because Gateway evaluates network and HTTP policies on every request, it maintai
 ```mermaid
 flowchart LR
 accTitle: Device posture policy enforcement
-A[Device] --schedule--> B[WARP client]--> C((Cloudflare)) --> D[Access policy]
+A[Device] --schedule--> B[Cloudflare One Client]--> C((Cloudflare)) --> D[Access policy]
 C --5 min--> E[Cache] --> F[Gateway policy]
 A --> G[Service provider] --interval--> C
 ```