[Cache] Updates plan information

src/content/docs/cache/how-to/purge-cache/index.mdx

@@ -14,4 +14,12 @@ Cloudflare's Instant Purge ensures that updates to your content are reflected im
 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.
 :::
 
+## Purge limits
+
 <FeatureTable id="cache.purge_cache" />
+
+### Token bucket rate limiting
+
+We use token bucket rate limiting to limit the number of purge requests flowing through the system at any given time, ensuring a steady and manageable flow. Each account tier has a defined request rate (for example, Free: 5 requests per minute, Business: 10 requests per second), and requests are only allowed if there are available tokens in the bucket. Tokens refill at a consistent rate, but each bucket has a maximum capacity (for example, Free: 25 tokens, Enterprise: 500 tokens), allowing short bursts of requests if tokens have accumulated. If the bucket is empty, further requests must wait until new tokens are added. This system maintains fair usage while allowing occasional bursts within the bucket's capacity.
+
+If you are an Enterprise customer and you need more operations, reach out to your account team for support. 

src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx

@@ -19,13 +19,7 @@ Purging by hostname means that all assets at URLs with a host that matches one o
 6. Enter the appropriate value(s) in the text field using the format shown in the example.
 7. Select **Purge**.
 
-:::note[API]
-
-
-You can purge hostnames via the Cloudflare API. For more information, refer to the [API documentation](/api/resources/cache/methods/purge/). You can use up to 30 hostnames per API call and make up to 30,000 purge API calls in a 24-hour period.
-
-
-:::
+For information on rate limits, refer to the [Purge limits](/cache/how-to/purge-cache/#purge-limits) section.
 
 ## Resulting cache status
 

src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx

@@ -7,7 +7,7 @@ sidebar:
 
 With purge by single-file, cached resources are instantly removed from the stored assets in your Content Delivery Network (CDN) across all data centers. New requests for the purged asset receive the latest version from your origin web server and add it back to your CDN cache within the specific Cloudflare data center that served the request.
 
-The single-file purge rate limit for the Free subscription is 1,000 URLs/minute. The rate limit is subject to change. For Zones on Free/Pro/Business plan, you may purge up to 30 URLs in one API call. For Zones on Enterprise plan, you may purge up to 500 URLs in one API call.
+For information on single-file purge rate limits, refer to the [Purge limits](/cache/how-to/purge-cache/#purge-limits) section.
 
 A single-file purge performed through your Cloudflare dashboard does not clear objects that contain any of the following:
 

src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx

@@ -53,14 +53,9 @@ When your content reaches our edge network, Cloudflare:
 5. In the text box, enter your tags to use to purge the cached resources. To purge multiple cache-tagged resources, separate each tag with a comma or have one tag per line.
 6. Select **Purge**.
 
-:::note[API]
+For information on rate limits, refer to the [Purge limits](/cache/how-to/purge-cache/#purge-limits) section.
 
 
-You can purge using cache-tags via the Cloudflare API. For more information, refer to the [API documentation](/api/resources/cache/methods/purge/). You can purge up to 30 cache-tags per API call and up to 250,000 cache-tags per a 24-hour period.
-
-
-:::
-
 ## Resulting cache status
 
 Purging by tag deletes the resource, resulting in the `CF-Cache-Status` header being set to [`MISS`](/cache/concepts/cache-responses/#miss) for subsequent requests.

src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx

@@ -30,13 +30,7 @@ Purging by prefix is useful in different scenarios, such as:
 6. Enter the appropriate value(s) in the text field using the format shown in the example.
 7. Select **Purge**.
 
-:::note[API]
-
-
-You can purge prefixes via the Cloudflare API. For more information, refer to the [API documentation](/api/resources/cache/methods/purge/). You can use up to 30 prefixes per API call and make up to 30,000 purge API calls in a 24-hour period.
-
-
-:::
+For information on rate limits, refer to the [Purge limits](/cache/how-to/purge-cache/#purge-limits) section.
 
 :::caution[Warning]
 

src/content/plans/index.json

@@ -437,10 +437,24 @@
 				},
 				"options": {
 					"title": "Purge options",
-					"free": "URL",
-					"pro": "URL",
-					"biz": "URL",
-					"ent": "URL, Hostname, Tag, or Prefix"
+					"free": "URL, Hostname, Tag, Prefix, and Purge Everything",
+                    "pro": "URL, Hostname, Tag, Prefix, and Purge Everything",
+                    "biz": "URL, Hostname, Tag, Prefix, and Purge Everything",
+                    "ent": "URL, Hostname, Tag, Prefix, and Purge Everything"
+                },
+                "limits": {
+                    "title": "Purge limits (tags, prefix URL, hostname, and purge everything). The limits are per account.",
+                    "free": "5 requests per minute with a bucket size of 25, supporting up to 100 operations per request. Purge everything: 5 requests per second with a bucket size of 25, supporting up to 100 operations per request",
+                    "pro": "5 requests per second with a bucket size of 25, supporting up to 100 operations per request",
+                    "biz": "10 requests per second with a bucket size of 50, supporting up to 100 operations per request",
+                    "ent": "50 requests per second with a bucket size of 500, supporting up to 100 operations per request"
+                },
+                "limits_single_file": {
+                    "title": "Purge limits (single file purge). The limits are per account.",
+                    "free": "800 urls per second",
+                    "pro": "1500 urls per second",
+                    "biz": "1500 urls per second",
+                    "ent": "3000 urls per second"
 				}
 			}
 		},