Apply in dns-firewall and fix {cluster_tag} with {dns_firewall_id}

Author: RebeccaTamachiro

src/content/docs/dns/dns-firewall/random-prefix-attacks/setup.mdx

@@ -9,22 +9,23 @@ head:
 
 ---
 
+import { APIRequest } from "~/components";
+
 In order to enable automatic mitigation of [random prefix attacks](/dns/dns-firewall/random-prefix-attacks/about/):
 
 1. Set up [DNS Firewall](/dns/dns-firewall/setup/).
 2. Send a [`PATCH` request](/api/resources/dns_firewall/methods/edit/) to update your DNS Firewall cluster.
 
-   ```bash
-   curl --request PATCH "https://api.cloudflare.com/client/v4/accounts/{account_id}/dns_firewall/{cluster_tag}" \
-   --header "Authorization: Bearer <API_TOKEN>" \
-   --header "Content-Type: application/json" \
-   --data '{
-     "attack_mitigation": {
-       "enabled": true,
-       "only_when_upstream_unhealthy": true
-     }
-   }'
-   ```
+   <APIRequest
+   	path="/accounts/{account_id}/dns_firewall/{dns_firewall_id}"
+   	method="PATCH"
+   	json={{
+      "attack_mitigation": {
+        "enabled": true,
+        "only_when_upstream_unhealthy": true,
+      }
+   	}}
+   />
 
 Once you receive a `200` success response from the API, queries identified as being part of a random prefix attack will receive a `REFUSED` response.