Added notes for cache request hostnames (#18634)

* Added two notes

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

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

* update with example

* Fixed

* made into note, simplified code example

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

Co-authored-by: Brendan Irvine-Broque <[email protected]>

* Changed to recommended approach

---------

Co-authored-by: Brendan Irvine-Broque <[email protected]>

Author: ToriLindsay

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

@@ -49,7 +49,17 @@ You may create and manage additional Cache instances via the [`caches.open`](htt
 let myCache = await caches.open('custom:cache');
 await myCache.match(request);
 ```
+:::note
+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.
+
+```js
+// recommended approach: use your Worker hostname to ensure efficient caching
+request.url = "https://your-Worker-hostname.com/";
 
+let myCache = await caches.open('custom:cache');
+let response = await myCache.match(request);
+```
+:::
 ***
 
 ## Headers
@@ -105,10 +115,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.
-
-
-:::
-
 #### Parameters
 
 
@@ -152,10 +158,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.
-
-
-:::
-
 #### Parameters