diff --git a/src/content/docs/byoip/address-maps/setup.mdx b/src/content/docs/byoip/address-maps/setup.mdx
index 06612e0bd227602..e0736c5d3fa90b6 100644
--- a/src/content/docs/byoip/address-maps/setup.mdx
+++ b/src/content/docs/byoip/address-maps/setup.mdx
@@ -6,7 +6,7 @@ sidebar:
label: Setup
---
-import { GlossaryTooltip, APIRequest } from "~/components";
+import { GlossaryTooltip, APIRequest, DashButton } from "~/components";
Consider the sections below to learn how to set up address maps.
@@ -20,13 +20,15 @@ To avoid any errors if you have [static IPs](/byoip/concepts/static-ips/), Cloud
If you are using BYOIP instead, refer to the following steps:
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
-2. Go to **IP Addresses** > **Address Maps**.
-3. Select **Create an address map**.
-4. Choose the scope of the address map.
-5. Add the zones and IP addresses that you want to map.
-6. Name your address map.
-7. Review the information and select **Save and Deploy**.
+1. In the Cloudflare dashboard, go to the **Address Maps** page.
+
+
+
+2. Select **Create an address map**.
+3. Choose the scope of the address map.
+4. Add the zones and IP addresses that you want to map.
+5. Name your address map.
+6. Review the information and select **Save and Deploy**.
:::note
Creating an address map does not automatically change DNS configuration. DNS responses only begin to change when a zone or account is added to a map. Additionally, address maps that are not yet enabled will not take effect in DNS responses.
@@ -34,11 +36,13 @@ Creating an address map does not automatically change DNS configuration. DNS res
## Manage address maps
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
-2. Go to **IP Addresses** > **Address Maps**.
-3. Go to your address map and select **Review**.
-4. Edit your address map.
-5. Review the information and select **Save**.
+1. In the Cloudflare dashboard, go to the **Address Maps** page.
+
+
+
+2. Go to your address map and select **Review**.
+3. Edit your address map.
+4. Review the information and select **Save**.
:::note
You can also enable, disable, and delete address maps. This will likely change the IP addresses used for your zones.
diff --git a/src/content/docs/byoip/route-leak-detection.mdx b/src/content/docs/byoip/route-leak-detection.mdx
index 41002bee519f7b2..6d26573e2003de6 100644
--- a/src/content/docs/byoip/route-leak-detection.mdx
+++ b/src/content/docs/byoip/route-leak-detection.mdx
@@ -6,7 +6,7 @@ sidebar:
---
-import { AvailableNotifications } from "~/components"
+import { AvailableNotifications, DashButton } from "~/components"
Route Leak Detection protects your routes on the Internet by notifying you when your traffic is routed somewhere it should not go, which could indicate a possible attack. Route Leak Detection also reduces the amount of time needed to mitigate leaks by providing you with timely notifications.
@@ -18,8 +18,11 @@ Cloudflare detects route leaks by using several sources of routing data to creat
You must be a user who has brought your own IP address to Cloudflare, which includes Magic Transit, Spectrum, and WAF users. Only prefixes advertised by Cloudflare qualify for Route Leak Detection.
-1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
-2. Select **Notifications** > **Add**.
+1. In the Cloudflare dashboard, go to the **Notifications** page.
+
+
+
+2. Select **Add**.
3. Locate **Route Leak Detection** from the list > **Select**.
4. Enter a name and description for the notification.
5. Enter one or more email addresses to receive the notifications.
diff --git a/src/content/docs/byoip/service-bindings/cdn-and-spectrum.mdx b/src/content/docs/byoip/service-bindings/cdn-and-spectrum.mdx
index 8b5a477609cc575..4ce5d8a028f3bf7 100644
--- a/src/content/docs/byoip/service-bindings/cdn-and-spectrum.mdx
+++ b/src/content/docs/byoip/service-bindings/cdn-and-spectrum.mdx
@@ -14,6 +14,7 @@ import {
TabItem,
Tabs,
GlossaryTooltip,
+ DashButton,
} from "~/components";
With [service bindings](/byoip/service-bindings/), CDN[^1] customers using BYOIP can take the same prefix they have onboarded to Cloudflare and use it to selectively route traffic on a per-IP address basis to [Spectrum](/spectrum/)[^2], or vice versa. This means:
@@ -98,13 +99,15 @@ If you need to map only specific subdomains (and not all proxied DNS records) to
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
-2. Go to **IP Addresses** > **Address Maps**.
-3. Select **Create an address map**.
-4. Choose the scope of the address map.
-5. Add the zones and IP addresses that you want to map.
-6. Name your address map.
-7. Review the information and select **Save and Deploy**.
+1. In the Cloudflare dashboard, go to the **Address Maps** page.
+
+
+
+2. Select **Create an address map**.
+3. Choose the scope of the address map.
+4. Add the zones and IP addresses that you want to map.
+5. Name your address map.
+6. Review the information and select **Save and Deploy**.
diff --git a/src/content/docs/byoip/service-bindings/magic-transit-with-cdn.mdx b/src/content/docs/byoip/service-bindings/magic-transit-with-cdn.mdx
index 1af5d48eb84896d..6ee5dc54278d4ca 100644
--- a/src/content/docs/byoip/service-bindings/magic-transit-with-cdn.mdx
+++ b/src/content/docs/byoip/service-bindings/magic-transit-with-cdn.mdx
@@ -14,6 +14,7 @@ import {
GlossaryTooltip,
APIRequest,
Render,
+ DashButton,
} from "~/components";
[Magic Transit](/magic-transit/) customers using BYOIP can also benefit from the performance, reliability, and security that Cloudflare offers for HTTP-based applications. [Service bindings](/byoip/service-bindings/) allow BYOIP customers to selectively route traffic on a per-IP address basis to the CDN pipeline (which includes [Cache](/cache/), [Web Application Firewall (WAF)](/waf/), and more).
@@ -71,13 +72,15 @@ If you need to map only specific subdomains (and not all proxied DNS records) to
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
-2. Go to **IP Addresses** > **Address Maps**.
-3. Select **Create an address map**.
-4. Choose the scope of the address map.
-5. Add the zones and IP addresses that you want to map.
-6. Name your address map.
-7. Review the information and select **Save and Deploy**.
+1. In the Cloudflare dashboard, go to the **Address Maps** page.
+
+
+
+2. Select **Create an address map**.
+3. Choose the scope of the address map.
+4. Add the zones and IP addresses that you want to map.
+5. Name your address map.
+6. Review the information and select **Save and Deploy**.
diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/managed-rulesets.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/managed-rulesets.mdx
index 51f67bc431cf6a2..f5cf43b38e3a8ac 100644
--- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/managed-rulesets.mdx
+++ b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/managed-rulesets.mdx
@@ -9,6 +9,8 @@ head:
---
+import { DashButton } from "~/components";
+
If you are interested in [WAF for SaaS](/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/) but unsure of where to start, Cloudflare recommends using WAF Managed Rules. The Cloudflare security team creates and manages a variety of rules designed to detect common attack vectors and protect applications from vulnerabilities. These rules are offered in [managed rulesets](/waf/managed-rules/), like Cloudflare Managed and OWASP, which can be deployed with different settings and sensitivity levels.
***
@@ -43,18 +45,16 @@ After the association is complete, the JSON blob is added to the defined custom
## 2. Deploy Rulesets
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and navigate to your account.
+1. In the Cloudflare dashboard, go to the **WAF** page.
-2. Select Account Home > **WAF**.
+
:::note
-
-
**WAF** at the account level will only be visible on Enterprise plans. If you do not see this option, contact your account manager.
-
-
:::
+2. Select **Managed rulesets**.
+
3. Select **Deploy a managed ruleset**.
4. Under **Field**, Select *Hostname*. Set the operator as *equals*. The complete expression should look like this, plus any logic you would like to add: