address comments

Author: dinasaur404

src/content/docs/cloudflare-for-platforms/workers-for-platforms/platform/worker-isolation.mdx

@@ -13,15 +13,14 @@ By default, Workers inside of a dispatch namespace are considered "untrusted." T
 In untrusted mode:
 
 - The [`request.cf`](/workers/runtime-apis/request/#incomingrequestcfproperties) object is not available in Workers (see [limits](/cloudflare-for-platforms/workers-for-platforms/platform/limits/#cf-object) for more information)
-- Each Worker has an isolated cache space when using the Cache API
-- Workers cannot access cached responses from other Workers in the namespace
+- Each Worker has an isolated cache, when using the [Cache API](/workers/runtime-apis/cache/) or when making subrequests using `fetch()`, which egress via [Cloudflare's cache](/cache/)
 - [`caches.default`](/workers/reference/how-the-cache-works/#cache-api) is disabled for all Workers in the namespace
 
 This mode ensures complete isolation between customer Workers, preventing any potential cross-tenant data access. 
 
 ### Trusted Mode
 
-If you control the Worker code and want to disable isolation mode, you can configure the namespace as "trusted".
+If you control the Worker code and want to disable isolation mode, you can configure the namespace as "trusted". This is useful when building internal platforms where your company controls all Worker code. 
 
 In trusted mode:
 
@@ -32,10 +31,6 @@ In trusted mode:
 In trusted mode, Workers can potentially access cached responses from other Workers in the namespace. Only enable this if you control all Worker code or have appropriate cache key isolation strategies.
 ::: 
 
-### Maintaining cache isolation in trusted mode
-If you need access to `request.cf` but want to maintain cache isolation between customers, use customer-specific [cache keys](/workers/examples/cache-using-fetch/#custom-cache-keys) or the [Cache API](/workers/examples/cache-api/) with isolated keys. 
-
-
 To convert a namespace from untrusted to trusted:
 ```bash
 curl -X PUT "https://api.cloudflare.com/client/v4/accounts/{account_id}/workers/dispatch/namespaces/{namespace_name}" \
@@ -49,6 +44,9 @@ curl -X PUT "https://api.cloudflare.com/client/v4/accounts/{account_id}/workers/
 
 If you enable trusted mode for a namespace that already has deployed Workers, you'll need to redeploy those Workers for the `request.cf` object to become available. Any new Workers you deploy after enabling trusted mode will automatically have access to it. 
 
+### Maintaining cache isolation in trusted mode
+If you need access to `request.cf` but want to maintain cache isolation between customers, use customer-specific [cache keys](/workers/examples/cache-using-fetch/#custom-cache-keys) or the [Cache API](/workers/examples/cache-api/) with isolated keys. 
+
 ## Related Resources
 * [Platform Limits](/cloudflare-for-platforms/workers-for-platforms/platform/limits) - Understanding script and API limits
 * [Cache API Documentation](/workers/runtime-apis/cache/) - Learn about cache behavior in Workers