update with example

Author: ToriLindsay

src/content/docs/workers/runtime-apis/cache.mdx

@@ -49,7 +49,16 @@ You may create and manage additional Cache instances via the [`caches.open`](htt
 let myCache = await caches.open('custom:cache');
 await myCache.match(request);
 ```
+When using the cache API, avoid overriding the hostname in cache requests, as this can lead to unnecessary DNS lookups and cache inefficiencies. Always use the hostname that matches the domain associated with your Worker.
 
+```async fetch(request, env, ctx) {
+    // avoid overriding the request URL or passing a new request into the cache API
+    request.url = "https://some-overridden-value.com";
+
+    let myCache = await caches.open('custom:cache');
+    await myCache.match(request);
+},
+```
 ***
 
 ## Headers
@@ -105,14 +114,6 @@ cache.put(request, response);
 
 
 The `stale-while-revalidate` and `stale-if-error` directives are not supported when using the `cache.put` or `cache.match` methods.
-
-
-:::
-
-:::note
-To avoid unnecessary DNS lookups and cache inefficiencies, do not override the hostname in cache requests. Always use the hostname that matches the domain associated with your Worker.
-:::
-
 #### Parameters
 
 
@@ -156,14 +157,6 @@ cache.match(request, options);
 
 
 The `stale-while-revalidate` and `stale-if-error` directives are not supported when using the `cache.put` or `cache.match` methods.
-
-
-:::
-
-:::note
-To avoid unnecessary DNS lookups and cache inefficiencies, do not override the hostname in cache requests. Always use the hostname that matches the domain associated with your Worker.
-:::
-
 #### Parameters