diff --git a/src/content/docs/cache/advanced-configuration/crawler-hints.mdx b/src/content/docs/cache/advanced-configuration/crawler-hints.mdx
index c025d7badb8ff6..fb07aa781bfd3d 100644
--- a/src/content/docs/cache/advanced-configuration/crawler-hints.mdx
+++ b/src/content/docs/cache/advanced-configuration/crawler-hints.mdx
@@ -4,7 +4,7 @@ title: Crawler Hints
---
-import { FeatureTable } from "~/components"
+import { FeatureTable, DashButton } from "~/components"
Crawler Hints aims to increase the proportion of relevant crawls and limit crawls that do not find fresh content to reduce the need for repeated crawls.
@@ -26,9 +26,11 @@ Crawler Hints also means less traffic hitting your origin, improving resource co
## Enable Crawler Hints
-1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com) and select your domain.
-2. Go to **Caching** > **Configuration**.
-3. Enable **Crawler Hints**.
+1. In the Cloudflare dashboard, go to the **Configuration** page.
+
+
+
+2. Enable **Crawler Hints**.
After enabling Crawler Hints, Cloudflare will begin sending hints to search engines about when they should crawl particular parts of your website.
diff --git a/src/content/docs/cache/cache-security/cache-deception-armor.mdx b/src/content/docs/cache/cache-security/cache-deception-armor.mdx
index d8755678542906..bffdae6da0e2b3 100644
--- a/src/content/docs/cache/cache-security/cache-deception-armor.mdx
+++ b/src/content/docs/cache/cache-security/cache-deception-armor.mdx
@@ -4,6 +4,8 @@ title: Cache Deception Armor
---
+import { DashButton } from "~/components";
+
Before learning about Cache Deception Armor, you should first understand how Web Cache Deception attacks work.
## Web Cache Deception attacks
@@ -30,10 +32,12 @@ In the newsfeed example above, if `http://www.example.com/newsfeed` is a script
To enable Cache Deception Armor, you need to start by creating a [cache rule](/cache/how-to/cache-rules/). Follow the steps below for guidance:
-1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and domain.
-2. Go to **Caching** > **Cache Rules**.
-3. Select **Create rule**.
-4. Under **When incoming requests match**, define the [rule expression](/ruleset-engine/rules-language/expressions/edit-expressions/#expression-builder).
-5. Under **Then**, in the **Cache eligibility** section, select **Eligible for cache**.
-6. Add the **Cache Key** setting to the rule and turn on **Cache deception armor**.
-7. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
+1. In the Cloudflare dashboard, go to the **Cache Rules** page.
+
+
+
+2. Select **Create rule**.
+3. Under **When incoming requests match**, define the [rule expression](/ruleset-engine/rules-language/expressions/edit-expressions/#expression-builder).
+4. Under **Then**, in the **Cache eligibility** section, select **Eligible for cache**.
+5. Add the **Cache Key** setting to the rule and turn on **Cache deception armor**.
+6. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
diff --git a/src/content/docs/cache/how-to/always-online.mdx b/src/content/docs/cache/how-to/always-online.mdx
index ab4562bcd651b3..4b318357b5d172 100644
--- a/src/content/docs/cache/how-to/always-online.mdx
+++ b/src/content/docs/cache/how-to/always-online.mdx
@@ -4,7 +4,7 @@ pcx_content_type: concept
---
-import { FeatureTable } from "~/components"
+import { FeatureTable, DashButton } from "~/components"
Cloudflare’s Always Online feature is now integrated with the [Internet Archive](https://archive.org/) so that visitors can access a portion of your website even when your origin server is unreachable and a Cloudflare-cached version is unavailable. When your origin is unreachable, Always Online checks Cloudflare’s cache for a stale or expired version of your website. If a version does not exist, Cloudflare goes to the Internet Archive to fetch and serve static portions of your website.
@@ -32,10 +32,12 @@ Visitors who interact with dynamic parts of a website, such as a shopping cart o
Here is how to enable Always Online in the dashboard:
-1. Log in to your Cloudflare account.
+1. In the Cloudflare dashboard, go to the **Configuration** page.
+
+
+
2. Choose the domain that will use Always Online with Internet Archive integration.
-3. Select **Caching** > **Configuration**.
-4. Under **Always Online**, set the toggle to **On**.
+3. Under **Always Online**, set the toggle to **On**.
:::note[Note]
diff --git a/src/content/docs/cache/how-to/cache-keys.mdx b/src/content/docs/cache/how-to/cache-keys.mdx
index d86a94a6397dc1..88beb5c3ec1223 100644
--- a/src/content/docs/cache/how-to/cache-keys.mdx
+++ b/src/content/docs/cache/how-to/cache-keys.mdx
@@ -7,7 +7,7 @@ head:
---
-import { FeatureTable } from "~/components"
+import { FeatureTable, DashButton } from "~/components"
A Cache Key is an identifier that Cloudflare uses for a file in our cache, and the Cache Key Template defines the identifier for a given HTTP request.
@@ -25,14 +25,16 @@ A default cache key includes:
Custom cache keys let you precisely set the cacheability setting for any resource. They provide the benefit of more control, though they may reduce your cache hit rate and result in cache sharding:
-1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com), and select your account and domain.
-2. Go to **Caching** > **Cache Rules**.
-3. Select **Create rule**.
-4. Under **When incoming requests match**, define the [rule expression](/ruleset-engine/rules-language/expressions/edit-expressions/#expression-builder).
-5. Under **Then**, in the **Cache eligibility** section, select **Eligible for cache**.
-6. Add the **Cache Key** setting to the rule and select the appropriate **Query String** setting.
-7. You can also select settings for **Headers**, **Cookie**, **Host**, and **User**.
-8. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
+1. In the Cloudflare dashboard, go to the **Cache Rules** page.
+
+
+
+2. Select **Create rule**.
+3. Under **When incoming requests match**, define the [rule expression](/ruleset-engine/rules-language/expressions/edit-expressions/#expression-builder).
+4. Under **Then**, in the **Cache eligibility** section, select **Eligible for cache**.
+5. Add the **Cache Key** setting to the rule and select the appropriate **Query String** setting.
+6. You can also select settings for **Headers**, **Cookie**, **Host**, and **User**.
+7. To save and deploy your rule, select **Deploy**. If you are not ready to deploy your rule, select **Save as Draft**.
:::note
When [URL normalization](/rules/normalization/) is enabled, we recommend also enabling [Normalize URLs to origin](/rules/normalization/manage/), especially if you are setting custom cache keys or using cache by device type, which also modifies the cache key. This helps ensure the URL in the cache key matches the URL sent to the origin, preventing cache poisoning and ensuring consistent behavior.
diff --git a/src/content/docs/cache/how-to/cache-rules/create-dashboard.mdx b/src/content/docs/cache/how-to/cache-rules/create-dashboard.mdx
index 47d79270fccf94..389b9eee392dc7 100644
--- a/src/content/docs/cache/how-to/cache-rules/create-dashboard.mdx
+++ b/src/content/docs/cache/how-to/cache-rules/create-dashboard.mdx
@@ -8,15 +8,17 @@ head:
content: Create a cache rule in the dashboard
---
-import { Render } from "~/components";
-
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
-2. Go to **Rules** > **Overview**.
-3. Next to **Cache Rules**, select **Create rule**.
-4. (Optional) Select one of the rule templates that address common use cases. Then, review and adjust the proposed rule configuration.
-5. Enter a descriptive name for the rule in **Rule name**.
-6. Under **When incoming requests match**, select **All incoming requests** if you want the rule to apply to all traffic or **Custom filter expression** if you want the rule to only apply to traffic matching the custom expression.
-7. If you selected **Custom filter expression**, under **When incoming requests match**, define the [rule expression](/ruleset-engine/rules-language/expressions/edit-expressions/#expression-builder). Use the **Field** drop-down list to choose an HTTP property and select an **Operator**. Refer to [Available settings](/cache/how-to/cache-rules/settings/) for the list of available fields and operators.
+import { Render, DashButton } from "~/components";
+
+1. In the Cloudflare dashboard, go to the **Cache Rules** page.
+
+
+
+2. Select **Create rule**.
+3. (Optional) Select one of the rule templates that address common use cases. Then, review and adjust the proposed rule configuration.
+4. Enter a descriptive name for the rule in **Rule name**.
+5. Under **When incoming requests match**, select **All incoming requests** if you want the rule to apply to all traffic or **Custom filter expression** if you want the rule to only apply to traffic matching the custom expression.
+6. If you selected **Custom filter expression**, under **When incoming requests match**, define the [rule expression](/ruleset-engine/rules-language/expressions/edit-expressions/#expression-builder). Use the **Field** drop-down list to choose an HTTP property and select an **Operator**. Refer to [Available settings](/cache/how-to/cache-rules/settings/) for the list of available fields and operators.
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 fde00aa755a1af..01adae3dd1f95a 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
@@ -6,18 +6,22 @@ sidebar:
---
+import { DashButton } from "~/components"
+
Purging by hostname means that all assets at URLs with a host that matches one of the provided values will be instantly purged from the cache.
-1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-2. Select **Caching** > **Configuration**.
-3. Under **Purge Cache**, select **Custom Purge**. The **Custom Purge** window appears.
-4. Under **Purge by**, select **Hostname**.
-5. Follow the syntax instructions:
+1. In the Cloudflare dashboard, go to the **Configuration** page.
+
+
+
+2. Under **Purge Cache**, select **Custom Purge**. The **Custom Purge** window appears.
+3. Under **Purge by**, select **Hostname**.
+4. Follow the syntax instructions:
* One hostname per line.
* Separated by commas.
* You can purge up to 30 hostnames at a time.
-6. Enter the appropriate value(s) in the text field using the format shown in the example.
-7. Select **Purge**.
+5. Enter the appropriate value(s) in the text field using the format shown in the example.
+6. Select **Purge**.
For information on rate limits, refer to the [Availability and limits](/cache/how-to/purge-cache/#availability-and-limits) section.
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 34bbc8cf6243ea..64bcee99f6d75b 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
@@ -5,6 +5,8 @@ sidebar:
order: 1
---
+import { DashButton } from "~/components"
+
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 [limits](/cache/how-to/purge-cache/#single-file-purge-limits) section.
@@ -27,14 +29,16 @@ You can purge objects with these characteristics using an API call to ([purge fi
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.
-2. Select **Caching** > **Configuration**.
-3. Under **Purge Cache**, select **Custom Purge**. The **Custom Purge** window appears.
-4. Under **Purge by**, select **URL**.
-5. Enter the appropriate value(s) in the text field using the format shown in the example. Be aware that the host part of the URL is not case-sensitive, meaning it will always be converted to lowercase according to RFC standards. However, the path portion is case-sensitive. For example, `https://EXAMPLE.com/helloHI` would be treated as `https://example.com/helloHI`.
-6. Perform any additional instructions to complete the form.
-7. Review your entries.
-8. Select **Purge**.
+1. In the Cloudflare dashboard, go to the **Configuration** page.
+
+
+
+2. Under **Purge Cache**, select **Custom Purge**. The **Custom Purge** window appears.
+3. Under **Purge by**, select **URL**.
+4. Enter the appropriate value(s) in the text field using the format shown in the example. Be aware that the host part of the URL is not case-sensitive, meaning it will always be converted to lowercase according to RFC standards. However, the path portion is case-sensitive. For example, `https://EXAMPLE.com/helloHI` would be treated as `https://example.com/helloHI`.
+5. Perform any additional instructions to complete the form.
+6. Review your entries.
+7. Select **Purge**.
:::note
For information on how to use single-file purge to purge assets cached by a Workers fetch, refer to [Single file purge assets cached by a Worker](/workers/reference/how-the-cache-works/#single-file-purge-assets-cached-by-a-worker).
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 ac23b85ba1aec4..ded86d4a602037 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
@@ -6,6 +6,8 @@ sidebar:
---
+import { DashButton } from "~/components"
+
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
@@ -46,12 +48,14 @@ When your content reaches our edge network, Cloudflare:
## Purge using cache-tags
-1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-2. Select **Caching** > **Configuration**.
-3. Under **Purge Cache**, select **Custom Purge**. The **Custom Purge** window appears.
-4. Under **Purge by**, select **Tag**.
-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**.
+1. In the Cloudflare dashboard, go to the **Configuration** page.
+
+
+
+2. Under **Purge Cache**, select **Custom Purge**. The **Custom Purge** window appears.
+3. Under **Purge by**, select **Tag**.
+4. 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.
+5. Select **Purge**.
For information on rate limits, refer to the [Availability and limits](/cache/how-to/purge-cache/#availability-and-limits) section.
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 e46fdf277c5f5d..6858616c43ddb1 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
@@ -6,14 +6,18 @@ sidebar:
---
+import { DashButton } from "~/components"
+
To maintain optimal site performance, Cloudflare strongly recommends using single-file (by URL) purging instead of a complete cache purge.
Purging everything instantly clears all resources from your CDN cache in all Cloudflare data centers. Each new request for a purged resource returns to your origin server to validate the resource. If Cloudflare cannot validate the resource, Cloudflare fetches the latest version from the origin server and replaces the cached version. When a site with heavy traffic contains a lot of assets, requests to your origin server can increase substantially and result in slow site performance.
-1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-2. Select **Caching** > **Configuration**.
-3. Under **Purge Cache**, select **Purge Everything**. A warning window appears.
-4. If you agree, select **Purge Everything**.
+1. In the Cloudflare dashboard, go to the **Configuration** page.
+
+
+
+2. Under **Purge Cache**, select **Purge Everything**. A warning window appears.
+3. 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.
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 b57f579b0e9c96..93a5ccc80e3bfe 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
@@ -6,6 +6,8 @@ sidebar:
---
+import { DashButton } from "~/components"
+
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`
@@ -20,15 +22,17 @@ Purging by prefix is useful in different scenarios, such as:
* Increasing control over cached objects in a path.
* Simplifying the number of purge calls sent.
-1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/login), and select your account and domain.
-2. Select **Caching** > **Configuration**.
-3. Under **Purge Cache**, select **Custom Purge**. The **Custom Purge** window appears.
-4. Under **Purge by**, select **Prefix**.
-5. Follow the syntax instructions.
+1. In the Cloudflare dashboard, go to the **Configuration** page.
+
+
+
+2. Under **Purge Cache**, select **Custom Purge**. The **Custom Purge** window appears.
+3. Under **Purge by**, select **Prefix**.
+4. Follow the syntax instructions.
* One prefix per line.
* Maximum 30 prefixes per API call.
-6. Enter the appropriate value(s) in the text field using the format shown in the example.
-7. Select **Purge**.
+5. Enter the appropriate value(s) in the text field using the format shown in the example.
+6. Select **Purge**.
For information on rate limits, refer to the [Availability and limits](/cache/how-to/purge-cache/#availability-and-limits) section.
diff --git a/src/content/docs/cache/how-to/tiered-cache.mdx b/src/content/docs/cache/how-to/tiered-cache.mdx
index 5bba44050fa83d..d4b1d745678b67 100644
--- a/src/content/docs/cache/how-to/tiered-cache.mdx
+++ b/src/content/docs/cache/how-to/tiered-cache.mdx
@@ -4,7 +4,7 @@ pcx_content_type: concept
---
-import { Details, FeatureTable, APIRequest, Render } from "~/components";
+import { Details, FeatureTable, APIRequest, Render, DashButton } from "~/components";
Tiered Cache uses the size of Cloudflare’s network to reduce requests to customer origins by dramatically increasing cache hit ratios. With data centers around the world, Cloudflare caches content very close to end users. However, if a piece of content is not in cache, the Cloudflare edge data centers must contact the origin server to receive the cacheable content.
@@ -54,10 +54,12 @@ You can enable Tiered Cache in the dashboard or via API.
### Enable Tiered Cache in the dashboard
-1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com) and select your domain.
-2. Select **Caching** > **Tiered Cache**.
-3. From **Tiered Cache**, toggle the button to **enabled**.
-4. In **Tiered Cache Topology**, you can control how your origin connects to Cloudflare’s data centers. You can select:
+1. In the Cloudflare dashboard, go to the **Tiered Cache** page.
+
+
+
+2. From **Tiered Cache**, toggle the button to **enabled**.
+3. In **Tiered Cache Topology**, you can control how your origin connects to Cloudflare’s data centers. You can select:
* **Upper Tier Cache** - You have the option to choose between Smart or Generic Global Tiered Cache Topology.
* **Middle Tier Cache** - If you have selected Smart or Custom Tiered Cache Topology, you can now enable Regional Tiered Cache.
* **Custom Tiered Cache** - Allows you to work with Cloudflare’s support team to set a custom topology that fits your specific needs.
diff --git a/src/content/docs/cache/performance-review/cache-analytics.mdx b/src/content/docs/cache/performance-review/cache-analytics.mdx
index 97450fde85934d..53d830ce69f172 100644
--- a/src/content/docs/cache/performance-review/cache-analytics.mdx
+++ b/src/content/docs/cache/performance-review/cache-analytics.mdx
@@ -4,7 +4,7 @@ pcx_content_type: concept
---
-import { FeatureTable } from "~/components"
+import { FeatureTable, DashButton } from "~/components"
Use Cache Analytics to improve site performance or reduce origin web server traffic. Cache Analytics helps determine if resources are missing from cache, expired, or ineligible for caching. Cache Analytics includes filter by hostname, list of top URLs that miss cache, and a query of up to three days of data.
@@ -14,8 +14,9 @@ Use Cache Analytics to improve site performance or reduce origin web server traf
## Access Cache Analytics
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain.
-2. Go to **Caching** > **Overview**.
+In the Cloudflare dashboard, go to the **Caching** page.
+
+
## Requests vs Data Transfer
diff --git a/src/content/docs/cache/reference/development-mode.mdx b/src/content/docs/cache/reference/development-mode.mdx
index 39f1d83d19e703..7256f57a19efad 100644
--- a/src/content/docs/cache/reference/development-mode.mdx
+++ b/src/content/docs/cache/reference/development-mode.mdx
@@ -4,6 +4,8 @@ pcx_content_type: how-to
---
+import { DashButton } from "~/components"
+
Development Mode temporarily suspends Cloudflare's edge caching and [Polish](/images/polish/) features for three hours unless disabled beforehand. Development Mode allows customers to immediately observe changes to their cacheable content like images, CSS, or JavaScript.
:::note
@@ -15,7 +17,8 @@ To bypass cache for longer than three hours, use bypass cache in [Cache Rules](/
Development Mode temporarily bypasses Cloudflare's cache and does not purge cached files. To instantly purge your Cloudflare cache, refer to [purge cache](/cache/how-to/purge-cache/).
-1. Log in to your Cloudflare account.
-2. Select your domain.
-3. Select **Caching**.
-4. Toggle **Development Mode** to **On**.
+1. In the Cloudflare dashboard, go to the **Configuration** page.
+
+
+
+2. Toggle **Development Mode** to **On**.
diff --git a/src/content/docs/data-localization/how-to/cache.mdx b/src/content/docs/data-localization/how-to/cache.mdx
index c2b5f6930c2ad1..bb6ad1c00b8f70 100644
--- a/src/content/docs/data-localization/how-to/cache.mdx
+++ b/src/content/docs/data-localization/how-to/cache.mdx
@@ -5,7 +5,7 @@ sidebar:
order: 3
---
-import { TabItem, Tabs } from "~/components";
+import { TabItem, Tabs, DashButton } from "~/components";
In the following sections, we will give you some details about how to configure Cache with Regional Services and Customer Metadata Boundary.
@@ -15,11 +15,13 @@ To configure Regional Services for hostnames [proxied](/dns/proxy-status/) throu
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select an account and zone.
-2. Go to the **DNS** tab.
-3. Follow these steps to [create a DNS record](/dns/manage-dns-records/how-to/create-dns-records/).
-4. From the **Region** dropdown, select the region you would like to use on your domain.
-5. Select **Save**.
+1. In the Cloudflare dashboard, go to the **Records** page.
+
+
+
+2. Follow these steps to [create a DNS record](/dns/manage-dns-records/how-to/create-dns-records/).
+3. From the **Region** dropdown, select the region you would like to use on your domain.
+4. Select **Save**.
diff --git a/src/content/docs/data-localization/how-to/load-balancing.mdx b/src/content/docs/data-localization/how-to/load-balancing.mdx
index 595b5be84317e8..49f8f4e1bf54e5 100644
--- a/src/content/docs/data-localization/how-to/load-balancing.mdx
+++ b/src/content/docs/data-localization/how-to/load-balancing.mdx
@@ -5,7 +5,7 @@ sidebar:
order: 4
---
-import { TabItem, Tabs } from "~/components";
+import { TabItem, Tabs, DashButton } from "~/components";
In the following sections, we will give you some details about how to configure Load Balancing with Regional Services and Customer Metadata Boundary.
@@ -17,12 +17,14 @@ To configure Regional Services for hostnames [proxied](/dns/proxy-status/) throu
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select an account and zone.
-2. Go to the **Load Balancing** tab.
-3. Follow the steps to [create a load balancer](/load-balancing/load-balancers/create-load-balancer/#create-a-load-balancer).
-4. From the **Data Localization** dropdown, select the region you would like to use on your domain.
-5. Select **Next** and continue with the regular setup.
-6. Select **Save**.
+1. In the Cloudflare dashboard, go to the **Load balancing** page.
+
+
+
+2. Follow the steps to [create a load balancer](/load-balancing/load-balancers/create-load-balancer/#create-a-load-balancer).
+3. From the **Data Localization** dropdown, select the region you would like to use on your domain.
+4. Select **Next** and continue with the regular setup.
+5. Select **Save**.
diff --git a/src/content/docs/health-checks/how-to/health-checks-notifications.mdx b/src/content/docs/health-checks/how-to/health-checks-notifications.mdx
index df31d236040f3f..d1ae4589f41e0b 100644
--- a/src/content/docs/health-checks/how-to/health-checks-notifications.mdx
+++ b/src/content/docs/health-checks/how-to/health-checks-notifications.mdx
@@ -6,21 +6,25 @@ sidebar:
---
+import { DashButton } from "~/components"
+
You can [configure notification emails](/health-checks/how-to/health-checks-notifications/#configure-notifications) to be alerted when the Health Check detects that there is a change in the status of your origin server. Cloudflare will send you an email within seconds so you can take the necessary action before customers are impacted.
The email provides information to determine what caused the health status change. You can evaluate when the change happened, the status of the origin server, if and why it is unhealthy, the expected response code, and the received response code.
## Configure notifications
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
-2. Navigate to **Traffic** > **Health Checks**.
-3. Select **Configure an alert**.
-4. Fill out the **Notification name** and **Description**.
-5. Add a Notification email.
-6. Select **Next**.
-7. Add health checks to include in your alerts.
-8. Choose the **Notification trigger**, which determines when you receive alerts.
-9. Select **Create**.
+1. In the Cloudflare dashboard, go to the **Health Checks** page.
+
+
+
+2. Select **Configure an alert**.
+3. Fill out the **Notification name** and **Description**.
+4. Add a Notification email.
+5. Select **Next**.
+6. Add health checks to include in your alerts.
+7. Choose the **Notification trigger**, which determines when you receive alerts.
+8. Select **Create**.
:::note
diff --git a/src/content/docs/speed/optimization/content/rocket-loader/enable.mdx b/src/content/docs/speed/optimization/content/rocket-loader/enable.mdx
index 416d64663e9728..98bad0cede714f 100644
--- a/src/content/docs/speed/optimization/content/rocket-loader/enable.mdx
+++ b/src/content/docs/speed/optimization/content/rocket-loader/enable.mdx
@@ -18,7 +18,7 @@ To enable or disable **Rocket Loader** in the dashboard:
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com).
2. Select your account and domain.
-3. Go to **Speed** > **Optimization** > **Content Optimization**.
+3. Go to **Speed** > **Settings** > **Content Optimization**.
4. For **Rocket Loader**, switch the toggle to **On**.
diff --git a/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx b/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx
index 3af64b5359c3b6..ff9cd7dd73c4d2 100644
--- a/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx
+++ b/src/content/docs/waiting-room/how-to/waiting-room-dashboard.mdx
@@ -6,11 +6,12 @@ sidebar:
---
+import { DashButton } from "~/components";
+
Use Cloudflare Waiting Room to create a holding area where users can queue to access a high-traffic area of your enterprise website. For an introduction, refer to the [Overview](/waiting-room/) page.
-To access Waiting Room on the Cloudflare dashboard:
+To access Waiting Room on the Cloudflare dashboard, go to the **Waiting Room** page.
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your application.
-2. Select **Traffic** > **Waiting Room**.
+
Use the dashboard to [create, edit, update, and delete](/waiting-room/how-to/) waiting rooms.
diff --git a/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx b/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx
index a841f69d3cf1c4..7bca9b160ea79e 100644
--- a/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx
+++ b/src/content/partials/spectrum/spectrum-with-load-balancer-dash.mdx
@@ -3,12 +3,16 @@
---
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login).
-2. Select **Spectrum**.
-3. Select **Create an Application**. If this is your first time using Spectrum, the **Create an Application** modal appears.
-4. Select your **[Application Type](/spectrum/reference/configuration-options/#application-type)**.
-5. Under **Domain**, enter the domain that will use Spectrum.
-6. Under **Edge Port**, enter the port Cloudflare should use for your application.
-7. Under **Origin**, select **Load Balancer**.
-8. Select the load balancer you want to use from the dropdown. Disabled load balancers will not show on the **Load Balancer** menu.
-9. Select **Add**.
+import { DashButton } from "~/components"
+
+1. In the Cloudflare dashboard, go to the **Spectrum** page.
+
+
+
+2. Select **Create an Application**. If this is your first time using Spectrum, the **Create an Application** modal appears.
+3. Select your **[Application Type](/spectrum/reference/configuration-options/#application-type)**.
+4. Under **Domain**, enter the domain that will use Spectrum.
+5. Under **Edge Port**, enter the port Cloudflare should use for your application.
+6. Under **Origin**, select **Load Balancer**.
+7. Select the load balancer you want to use from the dropdown. Disabled load balancers will not show on the **Load Balancer** menu.
+8. Select **Add**.