[Cache] Edits table (#21294)

* Edits table

* Removes enterprise mentions

Author: angelampcosta

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

@@ -24,7 +24,7 @@ A single-file purge performed through your Cloudflare dashboard does not clear o
 You can purge objects with these characteristics using an API call to ([purge files by URL](/api/resources/cache/methods/purge/)). In the data/header section of the API call, you must include all headers and cache keys contained in the cached resource, along with their matching values.
 
 :::caution
-Always use UTF-8 encoded URLs for single-file cache purges. Wildcards are not supported on single file purge, and you must use purge by hostname, prefix, or implement cache tags as an alternative solution. All of the listed options are Enterprise features.
+Always use UTF-8 encoded URLs for single-file cache purges. Wildcards are not supported on single file purge, and you must use purge by hostname, prefix, or implement cache tags as an alternative solution.
 :::
 
 1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.

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

@@ -6,7 +6,7 @@ sidebar:
 
 ---
 
-Cache-tag purging makes multi-file purging easier because you can instantly bulk purge by adding cache-tags to your assets, such as webpages, image files, and more. Note that Tag, Hostname and Prefix purges are only available for Enterprise customers.
+Cache-tag purging makes multi-file purging easier because you can instantly bulk purge by adding cache-tags to your assets, such as webpages, image files, and more.
 
 ## General workflow for cache-tags
 

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

@@ -6,7 +6,7 @@ sidebar:
 
 ---
 
-Enterprise customers can instantly purge their cache by URL prefix or path separators in their URL. For an example URL like `https://www.example.com/foo/bar/baz/qux.jpg`, valid purge requests include:
+You can instantly purge their cache by URL prefix or path separators in their URL. For an example URL like `https://www.example.com/foo/bar/baz/qux.jpg`, valid purge requests include:
 
 * `www.example.com`
 * `www.example.com/foo`

src/content/plans/index.json

@@ -444,7 +444,7 @@
                 },
                 "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",
+                    "free": "5 requests per minute 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"