diff --git a/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx b/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx
index 7de3391d9efb34..8414faa626b9af 100644
--- a/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx
+++ b/src/content/docs/cache/how-to/edge-browser-cache-ttl/set-browser-ttl.mdx
@@ -19,8 +19,6 @@ Nevertheless, the value you set via Cache Rule will be ignored if `Cache-Control
 
 ## Set Browser Cache TTL
 
-The Cloudflare UI and [API](/api/resources/zones/subresources/settings/methods/edit/) both prohibit setting Browser Cache TTL to 0 for non-Enterprise domains.
-
 :::note[Note]
 
 
@@ -34,11 +32,3 @@ If you modify cached assets, the new asset is not displayed to repeat visitors b
 3. Under **Browser Cache TTL**, select the drop-down menu to select the desired cache expiration time.
 
 The **Respect Existing Headers** option tells Cloudflare to honor the settings in the `Cache-Control` headers from your origin web server.
-
-:::note[Respect Existing Headers Availability]
-
-
-For all plan types, you can set Browser Cache TTL to Respect Existing Headers at a zone level (zone setting) or you can use a Cache Rule.
-
-
-:::
diff --git a/src/content/plans/index.json b/src/content/plans/index.json
index 70fa1212f38f2c..b46f9ed1f6b839 100644
--- a/src/content/plans/index.json
+++ b/src/content/plans/index.json
@@ -176,9 +176,9 @@
 					"ent": "30 seconds"
 				},
 				"minimum_cache_rules": {
-					"title": "Minimum Browser Cache TTL (Cache Rules)",
-					"free": "2 hours",
-					"pro": "1 hour",
+					"title": "Minimum Browser Cache TTL",
+					"free": "1 second",
+					"pro": "1 second",
 					"biz": "1 second",
 					"ent": "1 second"
 				},