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 2e636e5d23316c5..08f0b98a94bb2ad 100644 --- a/src/content/docs/cache/how-to/purge-cache/index.mdx +++ b/src/content/docs/cache/how-to/purge-cache/index.mdx @@ -14,7 +14,7 @@ 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 +## Availability and limits diff --git a/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx b/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx index ffc510d6f8558c5..fde00aa755a1af4 100644 --- a/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx +++ b/src/content/docs/cache/how-to/purge-cache/purge-by-hostname.mdx @@ -19,7 +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**. -For information on rate limits, refer to the [Purge limits](/cache/how-to/purge-cache/#purge-limits) section. +For information on rate limits, refer to the [Availability and limits](/cache/how-to/purge-cache/#availability-and-limits) section. ## Resulting cache status diff --git a/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx b/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx index 42a8e732606350d..31c5cb1c2fea88b 100644 --- a/src/content/docs/cache/how-to/purge-cache/purge-by-single-file.mdx +++ b/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. -For information on single-file purge rate limits, refer to the [Purge limits](/cache/how-to/purge-cache/#purge-limits) section. +For information on single-file purge rate limits, refer to the [limits](/cache/how-to/purge-cache/#single-file-purge-limits) section. A single-file purge performed through your Cloudflare dashboard does not clear objects that contain any of the following: diff --git a/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx b/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx index 47aa715382b4f52..594bb1849c61246 100644 --- a/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx +++ b/src/content/docs/cache/how-to/purge-cache/purge-by-tags.mdx @@ -53,7 +53,7 @@ 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**. -For information on rate limits, refer to the [Purge limits](/cache/how-to/purge-cache/#purge-limits) section. +For information on rate limits, refer to the [Availability and limits](/cache/how-to/purge-cache/#availability-and-limits) section. ## Resulting cache status 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 4a927cee751c285..e46fdf277c5f5dd 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 @@ -19,6 +19,8 @@ Purging everything instantly clears all resources from your CDN cache in all Clo 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. ::: +For information on rate limits, refer to the [Availability and limits](/cache/how-to/purge-cache/#availability-and-limits) section. + ## 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/docs/cache/how-to/purge-cache/purge_by_prefix.mdx b/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx index bb31e38c08b93ec..b57f579b0e9c969 100644 --- a/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx +++ b/src/content/docs/cache/how-to/purge-cache/purge_by_prefix.mdx @@ -30,7 +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**. -For information on rate limits, refer to the [Purge limits](/cache/how-to/purge-cache/#purge-limits) section. +For information on rate limits, refer to the [Availability and limits](/cache/how-to/purge-cache/#availability-and-limits) section. :::caution[Warning]