Edit steps to account for PAC files

Author: maxvp

src/content/docs/cloudflare-one/connections/connect-devices/agentless/pac-files.mdx

@@ -13,7 +13,7 @@ Only available on Enterprise plans.
 
 You can apply Gateway HTTP and DNS policies at the browser level by configuring a Proxy Auto-Configuration (PAC) file.
 
-<GlossaryDefinition term="PAC file" prepend="A PAC file is" />
+<GlossaryDefinition term="PAC file" prepend="A PAC file is " />
 
 When end users visit a website, their browser will send the request to a Cloudflare proxy server associated with your account to be filtered by Gateway. Note that Gateway [cannot filter every type of HTTP traffic](#limitations) proxied using PAC files.
 
@@ -217,17 +217,15 @@ To get the domain of a proxy endpoint:
 
    ```json {10} output
    {
-    "success": true,
-    "result": {
-      "id": "ed35569b41ce4d1facfe683550f54086",
-      "created_at": "2014-01-01T05:20:00.12345Z",
-      "ips": [
-        "192.0.2.1/32"
-      ],
-      "name": "DevOps team",
-      "subdomain": "oli3n9zkz5.proxy.cloudflare-gateway.com",
-      "updated_at": "2014-01-01T05:20:00.12345Z"
-    }
+   	"success": true,
+   	"result": {
+   		"id": "ed35569b41ce4d1facfe683550f54086",
+   		"created_at": "2014-01-01T05:20:00.12345Z",
+   		"ips": ["192.0.2.1/32"],
+   		"name": "DevOps team",
+   		"subdomain": "oli3n9zkz5.proxy.cloudflare-gateway.com",
+   		"updated_at": "2014-01-01T05:20:00.12345Z"
+   	}
    }
    ```
 

src/content/docs/cloudflare-one/policies/gateway/proxy.mdx

@@ -15,11 +15,11 @@ The Gateway proxy is required for filtering HTTP and network traffic via the WAR
 
 Gatway uses the [Happy Eyeballs algorithm](https://datatracker.ietf.org/doc/html/rfc6555) to proxy traffic in the following order:
 
-1. The user's WARP client initiates the TCP handshake by sending Gateway a TCP SYN segment.
+1. The user's browser initiates the TCP handshake by sending Gateway a TCP SYN segment.
 2. Gateway sends a SYN segment to the origin server.
-3. If the origin server sends a SYN-ACK segment back, Gateway establishes distinct TCP connections between the WARP client and Gateway and between Gateway and the origin server.
-4. Gateway inspects and filters traffic received from the WARP client.
-5. If the traffic passes inspection, Gateway proxies traffic bidirectionally between the client and the origin server.
+3. If the origin server sends a SYN-ACK segment back, Gateway establishes distinct TCP connections between the user and Gateway and between Gateway and the origin server.
+4. Gateway inspects and filters traffic received from the user.
+5. If the traffic passes inspection, Gateway proxies traffic bidirectionally between the user and the origin server.
 
 ```mermaid
 flowchart TD