final update

Author: deadlypants1973

src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx

@@ -38,7 +38,7 @@ If `<url>` is not provided, users are presented with a Cloudflare Zero Trust lan
 
 ### Allow or block websites
 
-When users visit a website through the [Clientless Web Isolation URL](#use-the-remote-browser), the traffic passes through Cloudflare Gateway. This allows you to [apply HTTP policies](/cloudflare-one/policies/gateway/http-policies/) to control what websites the remote browser can connect to, even if the user's device does not have WARP installed.
+When users visit a website through the [Clientless Web Isolation URL](#use-the-remote-browser), the traffic passes through Cloudflare Gateway. This allows you to [apply HTTP policies](/cloudflare-one/policies/gateway/http-policies/) to control what websites the remote browser can connect to, even if the user's device does not have WARP installed. 
 
 For example, if you use a third-party Secure Web Gateway to block `example.com`, users can still access the page in the remote browser by visiting `https://<your-team-name>.cloudflareaccess.com/browser/https://www.example.com/`. To block `https://<your-team-name>.cloudflareaccess.com/browser/https://www.example.com/`, create a Cloudflare Gateway HTTP policy to block `example.com`:
 
@@ -56,7 +56,7 @@ If [TLS decryption](/cloudflare-one/policies/gateway/http-policies/tls-decryptio
 
 :::note
 
-TLS decryption is not required to apply HTTP policies to Clientless Web Isolation traffic. However, enabling TLS decryption is necessary if you want to add [Data Loss Prevention (DLP)](/cloudflare-one/policies/data-loss-prevention/) configurations.
+Clientless Web Isolation can function without TLS decryption enabled. However, TLS decryption is required to apply HTTP policies to Clientless Web Isolation traffic.
 
 :::