Create and apply cache-reserve-operations partial

Author: RebeccaTamachiro

src/content/docs/cache/advanced-configuration/cache-reserve.mdx

@@ -100,27 +100,10 @@ For example:
 
 ### Operations
 
-Operations are performed by Cache Reserve on behalf of the user to write data from the origin to Cache Reserve and to pass that data downstream to other parts of Cloudflare’s network. These operations are managed internally by Cloudflare.
-
-#### Class A operations (writes)
-
-Class A operations are performed based on cache misses from Cloudflare’s CDN. When a request cannot be served from cache, it will be fetched from the origin and written to cache reserve as well as our edge caches on the way back to the visitor.
-
-#### Class B operations (reads)
-
-Class B operations are performed when data needs to be fetched from Cache Reserve to respond to a miss in the edge cache.
-
-#### Purge
-
-Asset purges are free operations.
-
-Cache Reserve will be instantly purged along with edge cache when you send a purge by URL request.
-
-Other purge methods, such as purge by tag, host, prefix, or purge everything will force an attempt to [revalidate](/cache/concepts/cache-responses/#revalidated) on the subsequent request for the Cache Reserve asset. Note that assets purged this way will still incur storage costs until their retention TTL expires.
-
-:::note
-Note this differs from the standard CDN's purge by tag, host, or prefix features which force a cache miss, requiring the origin to deliver the asset in full.
-:::
+<Render
+  file="cache-reserve-operations"
+  product="cache"
+/>
 
 ## Cache Reserve billing examples
 

src/content/docs/smart-shield/configuration/cache-reserve/operations.mdx

@@ -5,3 +5,10 @@ sidebar:
   order: 2
   label: Operations
 ---
+
+import { Render } from "~/components";
+
+<Render
+  file="cache-reserve-operations"
+  product="cache"
+/>

src/content/partials/cache/cache-reserve-operations.mdx

@@ -0,0 +1,25 @@
+---
+{}
+---
+
+Operations are performed by Cache Reserve on behalf of the user to write data from the origin to Cache Reserve and to pass that data downstream to other parts of Cloudflare’s network. These operations are managed internally by Cloudflare.
+
+#### Class A operations (writes)
+
+Class A operations are performed based on cache misses from Cloudflare’s CDN. When a request cannot be served from cache, it will be fetched from the origin and written to cache reserve as well as our edge caches on the way back to the visitor.
+
+#### Class B operations (reads)
+
+Class B operations are performed when data needs to be fetched from Cache Reserve to respond to a miss in the edge cache.
+
+#### Purge
+
+Asset purges are free operations.
+
+Cache Reserve will be instantly purged along with edge cache when you send a purge by URL request. Refer to [cache configurations](/cache/how-to/purge-cache/) for details.
+
+Other purge methods, such as purge by tag, host, prefix, or purge everything will force an attempt to [revalidate](/cache/concepts/cache-responses/#revalidated) on the subsequent request for the Cache Reserve asset. Note that assets purged this way will still incur storage costs until their retention TTL expires.
+
+:::note
+Note this differs from the standard CDN's purge by tag, host, or prefix features which force a cache miss, requiring the origin to deliver the asset in full.
+:::