diff --git a/src/content/docs/cache/how-to/cache-rules/index.mdx b/src/content/docs/cache/how-to/cache-rules/index.mdx
index 9c1041816edff7..3b22f3d39b8e13 100644
--- a/src/content/docs/cache/how-to/cache-rules/index.mdx
+++ b/src/content/docs/cache/how-to/cache-rules/index.mdx
@@ -9,6 +9,11 @@ Use Cache Rules to customize cache settings on Cloudflare. Cache Rules allows yo
 
 Cache Rules can be created in the [dashboard](/cache/how-to/cache-rules/create-dashboard/), via [API](/cache/how-to/cache-rules/create-api/) or [Terraform](/cache/how-to/cache-rules/terraform-example/).
 
+:::note
+Rules can be versioned. Refer to the [Version Management](/version-management/) documentation for more information.
+:::
+
+
 ## Rules templates
 
 <Render file="rules-templates" product="rules" />
diff --git a/src/content/docs/cache/how-to/purge-cache/index.mdx b/src/content/docs/cache/how-to/purge-cache/index.mdx
index 85374c528234bf..b0a5e585373971 100644
--- a/src/content/docs/cache/how-to/purge-cache/index.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/index.mdx
@@ -10,4 +10,8 @@ Cloudflare's Instant Purge ensures that updates to your content are reflected im
 
 <DirectoryListing />
 
+:::note
+If versioning is active on your zone and multiple environments are configured, you can select the specific environment you want to purge. For more details, refer to the [Version Management](/version-management/) documentation.
+:::
+
 <FeatureTable id="cache.purge_cache" />
diff --git a/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx b/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx
index 6b1ba5f5372621..4a927cee751c28 100644
--- a/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx
+++ b/src/content/docs/cache/how-to/purge-cache/purge-everything.mdx
@@ -15,6 +15,10 @@ Purging everything instantly clears all resources from your CDN cache in all Clo
 3. Under **Purge Cache**, select **Purge Everything**. A warning window appears.
 4. If you agree, select **Purge Everything**.
 
+:::note
+When purging everything for a non-production cache environment, all files for that specific cache environment will be purged. However, when purging everything for the production environment, all files will be purged across all environments.
+:::
+
 ## Resulting cache status
 
 Purge Everything invalidates the resource, resulting in the `CF-Cache-Status` header indicating [`EXPIRED`](/cache/concepts/cache-responses/#expired) for subsequent requests.
diff --git a/src/content/partials/version-management/product-limitations.mdx b/src/content/partials/version-management/product-limitations.mdx
index 7e438a84a3284b..5e20b8d6629fe2 100644
--- a/src/content/partials/version-management/product-limitations.mdx
+++ b/src/content/partials/version-management/product-limitations.mdx
@@ -22,10 +22,8 @@ Version Management does not currently support or have limited support for the fo
 
 <Details header="Cache">
 
-- [Cache](/workers/runtime-apis/cache/) configurations are versioned, but cache keys are not.
-- Caching a new URL on staging would cache it for production as well.
-- Purging cache on staging would purge it on production too.
-- Promoting a new version to production would wipe all exiting cache.
+- [Cache Reserve](/cache/advanced-configuration/cache-reserve/) is intended for production use only.
+- [Tiered Cache](/cache/how-to/tiered-cache/) does not support versioning.
 
 </Details>