Replace remaining /zones/{zone_id}/dns_settings examples

Author: RebeccaTamachiro

src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx

@@ -94,16 +94,13 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/dns_records" \
 This step is required. Without turning on this setting, Cloudflare will ignore any `NS` records created on the zone apex. This means that responses to DNS queries made to the zone apex and requesting `NS` records will only contain Cloudflare nameservers.
 :::
 
-```bash
-curl --request PATCH \
-"https://api.cloudflare.com/client/v4/zones/{zone_id}/dns_settings" \
---header "X-Auth-Email: <EMAIL>" \
---header "X-Auth-Key: <API_KEY>" \
---header "Content-Type: application/json" \
---data '{
-    "multi_provider": true
-}'
-```
+<APIRequest
+	path="/zones/{zone_id}/dns_settings"
+	method="PATCH"
+	json={{
+		"multi_provider": true,
+	}}
+/>
 
 </TabItem>
 </Tabs>

src/content/docs/dns/foundation-dns/setup.mdx

@@ -6,7 +6,7 @@ sidebar:
   label: Setup
 ---
 
-import { TabItem, Tabs } from "~/components";
+import { TabItem, Tabs, APIRequest } from "~/components";
 
 Advanced nameservers included with [Foundation DNS](/dns/foundation-dns/) are an opt-in configuration.
 
@@ -27,16 +27,13 @@ To enable advanced nameservers on an existing zone:
 
     Use the [Update DNS Settings](/api/resources/dns/subresources/settings/methods/edit/) endpoint to send a PATCH request like the following:
 
-    ```bash
-    curl --request PATCH \
-    "https://api.cloudflare.com/client/v4/zones/{zone_id}/dns_settings" \
-    --header "X-Auth-Email: <EMAIL>" \
-    --header "X-Auth-Key: <API_KEY>" \
-    --header "Content-Type: application/json" \
-    --data '{
-      "foundation_dns": true
-    }'
-    ```
+  	<APIRequest
+  	path="/zones/{zone_id}/dns_settings"
+  	method="PATCH"
+  	json={{
+  		"foundation_dns": true,
+  	}}
+    />
 
     The response body will contain your assigned namservers in the `nameservers` object. You will use these nameservers in the next step.