[Workers]

Explicitly state that Cache Reserve is not supported.

Author: markdembo

src/content/docs/workers/reference/how-the-cache-works.mdx

@@ -26,10 +26,10 @@ Conceptually, there are two ways to interact with Cloudflare’s Cache using a W
 
   * Caching responses generated by the Worker itself through `cache.put()`.
 
-:::caution[Tiered caching]
+:::caution[Tiered caching & Cache Reserve]
 
 
-The Cache API is not compatible with tiered caching. To take advantage of tiered caching, use the [fetch API](/workers/runtime-apis/fetch/).
+The Cache API is not compatible with tiered caching and Cache Reserve. To take advantage of tiered caching, use the [fetch API](/workers/runtime-apis/fetch/).
 
 
 :::
@@ -118,7 +118,7 @@ This [template](/workers/examples/cache-api/) shows ways to use the cache API. F
 
 :::caution[Tiered caching and the Cache API]
 
-Cache API within Workers does not support tiered caching. Tiered Cache concentrates connections to origin servers so they come from a small number of data centers rather than the full set of network locations. Cache API is local to a data center, this means that `cache.match` does a lookup, `cache.put` stores a response, and `cache.delete` removes a stored response only in the cache of the data center that the Worker handling the request is in. Because these methods apply only to local cache, they will not work with tiered cache. 
+Cache API within Workers does not support tiered caching or use with Cache Reserve. Tiered Cache concentrates connections to origin servers so they come from a small number of data centers rather than the full set of network locations. Cache API is local to a data center, this means that `cache.match` does a lookup, `cache.put` stores a response, and `cache.delete` removes a stored response only in the cache of the data center that the Worker handling the request is in. Because these methods apply only to local cache, they will not work with tiered cache. 
 :::
 
 ## Related resources