Double-check and remove original bash throughout

RebeccaTamachiro · RebeccaTamachiro · commit 9f78d3c8aafd · 2025-05-16T10:38:42.000+01:00
diff --git a/src/content/docs/ssl/client-certificates/byo-ca.mdx b/src/content/docs/ssl/client-certificates/byo-ca.mdx
@@ -95,12 +95,6 @@ If you want to remove a CA that you have previously uploaded, you must first rem
 
 You can also use the [API](/api/resources/certificate_authorities/subresources/hostname_associations/methods/get/) to list the hostname associations. Make sure you include the query parameter `mtls_certificate_id`, where `mtls_certificate_id` is the certificate ID of the uploaded CA (step 2 above).
 
-```bash
-curl "https://api.cloudflare.com/client/v4/zones/zone_id/certificate_authorities/hostname_associations?mtls_certificate_id={id_from_step_2}"  \
---header "X-Auth-Email: <EMAIL>" \
---header "X-Auth-Key: <API_KEY>"
-```
-
 <APIRequest
   path="/zones/{zone_id}/certificate_authorities/hostname_associations"
   method="GET"
diff --git a/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx b/src/content/docs/ssl/edge-certificates/additional-options/minimum-tls.mdx
@@ -54,17 +54,6 @@ Use the [Edit zone setting](/api/resources/zones/subresources/settings/methods/e
 
 In the following example, the minimum TLS version for the zone will be set to `1.2`. Replace the zone ID and API token placeholders with your information, and adjust the `value` field with your chosen TLS version.
 
-```bash
-curl --request PATCH \
-"https://api.cloudflare.com/client/v4/zones/{zone_id}/settings/min_tls_version" \
---header "Authorization: Bearer <API_TOKEN>" \
---header "Content-Type: application/json" \
---data '{
-    "id": "min_tls_version",
-    "value": "1.2"
-  }'
-```
-
 <APIRequest
   path="/zones/{zone_id}/settings/{setting_id}"
   method="PATCH"
@@ -90,17 +79,7 @@ This is currently only available via the API:
 
 Cloudflare uses the [hostname priority logic](/ssl/reference/certificate-and-hostname-priority/) to determine which setting to apply.
 
-In the following example, the minimum TLS version for a specific hostname will be set to `1.2`. Replace the zone ID, hostname, and API token placeholders with your information, and adjust the `value` field with your chosen TLS version.
-
-```bash
-curl --request PUT \
-"https://api.cloudflare.com/client/v4/zones/{zone_id}/hostnames/settings/min_tls_version/{hostname}" \
---header "Authorization: Bearer <API_TOKEN>" \
---header "Content-Type: application/json" \
---data '{
-    "value": "1.2"
-  }'
-```
+In the following example, the minimum TLS version for a specific hostname will be set to `1.2`. Replace the zone ID, hostname, and authentication placeholders with your information, and adjust the `value` field with your chosen TLS version.
 
 <APIRequest
   path="/zones/{zone_id}/hostnames/settings/{setting_id}/{hostname}"
diff --git a/src/content/docs/ssl/edge-certificates/geokey-manager/setup.mdx b/src/content/docs/ssl/edge-certificates/geokey-manager/setup.mdx
@@ -10,7 +10,7 @@ description: Learn how to set up Geo Key Manager and choose the geographical
   boundaries of where your private encryption keys are stored.
 ---
 
-import { Render, TabItem, Tabs, InlineBadge, APIRequest } from "~/components";
+import { Render, TabItem, Tabs, InlineBadge, APIRequest, Example } from "~/components";
 
 ## Geo Key Manager v2 <InlineBadge preset="beta" />
 
@@ -36,18 +36,9 @@ You also have access to the `geo_restrictions` parameter, which is mutually excl
 
 ### Examples
 
-```bash title="Store private keys in the E.U. and the U.S."
-curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_certificates" \
---header "X-Auth-Email: <EMAIL>" \
---header "X-Auth-Key: <API_KEY>" \
---header "Content-Type: application/json" \
---data '{
-  "certificate":"certificate",
-  "private_key":"<PRIVATE_KEY>",
-  "policy":"(country: US) and (region: EU)",
-  "type": "sni_custom"
-}'
-```
+<Example>
+
+Store private keys in the E.U. and the U.S.
 
 <APIRequest
   path="/zones/{zone_id}/custom_certificates"
@@ -60,18 +51,10 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_certificates"
 	}}
 />
 
-```bash title="Store private keys in the E.U., but not in France"
-curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_certificates" \
---header "X-Auth-Email: <EMAIL>" \
---header "X-Auth-Key: <API_KEY>" \
---header "Content-Type: application/json" \
---data '{
-  "certificate":"certificate",
-  "private_key":"<PRIVATE_KEY>",
-  "policy":"(region: EU) and (not country: FR)",
-  "type": "sni_custom"
-}'
-```
+</Example>
+
+<Example>
+Store private keys in the E.U., but not in France
 
 <APIRequest
   path="/zones/{zone_id}/custom_certificates"
@@ -84,6 +67,8 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_certificates"
 	}}
 />
 
+</Example>
+
 :::note
 
 For more information on the `policy` field, refer to [Supported options](/ssl/edge-certificates/geokey-manager/supported-options/).
diff --git a/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/aws-alb-integration.mdx b/src/content/docs/ssl/origin-configuration/authenticated-origin-pull/aws-alb-integration.mdx
@@ -71,23 +71,6 @@ curl --verbose https://<your-application-load-balancer>
 
 2.[Associate the certificate with the hostname](/api/resources/origin_tls_client_auth/subresources/hostnames/methods/update/) that should use it.
 
-```bash
-curl --silent --request PUT \
-"https://api.cloudflare.com/client/v4/zones/$ZONEID/origin_tls_client_auth/hostnames" \
---header "Content-Type: application/json" \
---header "X-Auth-Email: $MYAUTHEMAIL" \
---header "X-Auth-Key: $MYAUTHKEY" \
---data '{
-  "config": [
-    {
-      "enabled": true,
-      "cert_id": "<CERT_ID>",
-      "hostname": "<YOUR_HOSTNAME>"
-    }
-  ]
-}'
-```
-
 <APIRequest
   path="/zones/{zone_id}/origin_tls_client_auth/hostnames"
   method="PUT"
@@ -105,17 +88,6 @@ curl --silent --request PUT \
 
 3. [Enable the Authenticated Origin Pulls](/ssl/origin-configuration/authenticated-origin-pull/set-up/per-hostname/#3-enable-authenticated-origin-pulls-globally) feature on your zone.
 
-```bash
-curl --request PATCH \
-"https://api.cloudflare.com/client/v4/zones/$ZONEID/settings/tls_client_auth" \
---header "X-Auth-Email: $MYAUTHEMAIL" \
---header "X-Auth-Key: $MYAUTHKEY" \
---header "Content-Type: application/json" \
---data '{
-  "value": "on"
-}'
-```
-
 <APIRequest
   path="/zones/{zone_id}/settings/{setting_id}"
   method="PATCH"
@@ -139,23 +111,6 @@ Make sure your [encryption mode](/ssl/origin-configuration/ssl-modes/) is set to
 
 1. Use a [`PUT` request](/api/resources/origin_tls_client_auth/subresources/hostnames/methods/update/) to disable Authenticated Origin Pulls on the hostname.
 
-```bash
-curl -s --request PUT \
-"https://api.cloudflare.com/client/v4/zones/$ZONEID/origin_tls_client_auth/hostnames" \
---header "Content-Type: application/json" \
---header "X-Auth-Email: $MYAUTHEMAIL" \
---header "X-Auth-Key: $MYAUTHKEY" \
---data '{
-  "config": [
-    {
-      "enabled": false,
-      "cert_id": "<CERT_ID>",
-      "hostname": "<YOUR_HOSTNAME>"
-    }
-  ]
-}'
-```
-
 <APIRequest
   path="/zones/{zone_id}/origin_tls_client_auth/hostnames"
   method="PUT"
@@ -173,27 +128,13 @@ curl -s --request PUT \
 
 2. (Optional) Use a [`GET` request](/api/resources/origin_tls_client_auth/subresources/hostnames/subresources/certificates/methods/list/) to obtain a list of the client certificate IDs. You will need the ID of the certificate you want to remove for the following step.
 
-```bash
-curl "https://api.cloudflare.com/client/v4/zones/$ZONEID/origin_tls_client_auth/hostnames/certificates" \
---header "X-Auth-Email: $MYAUTHEMAIL" \
---header "X-Auth-Key: $MYAUTHKEY"
-```
-
 <APIRequest
   path="/zones/{zone_id}/origin_tls_client_auth/hostnames/certificates"
   method="GET"
 />
 
-
 3. Use the [Delete hostname client certificate](/api/resources/origin_tls_client_auth/subresources/hostnames/subresources/certificates/methods/delete/) endpoint to remove the certificate you had uploaded.
 
-```bash
-curl --request DELETE \
-"https://api.cloudflare.com/client/v4/zones/$ZONEID/origin_tls_client_auth/hostnames/certificates/$CERTID" \
---header "X-Auth-Email: $MYAUTHEMAIL" \
---header "X-Auth-Key: $MYAUTHKEY"
-```
-
 <APIRequest
   path="/zones/{zone_id}/origin_tls_client_auth/hostnames/certificates/{certificate_id}"
   method="DELETE"
diff --git a/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx b/src/content/docs/ssl/origin-configuration/ssl-modes/index.mdx
@@ -52,15 +52,6 @@ Automatic SSL/TLS will not change your setting to a less secure encryption mode.
 
 If you want to opt a zone out via the API, you can make this API call on or before the grace period expiration date.
 
-```bash
- curl --request PATCH \
-  --url https://api.cloudflare.com/client/v4/zones/<ZONE_ID>/settings/ssl_automatic_mode \
-  --header 'Authorization: Bearer <CF_API_TOKEN>' \
-  --header 'Content-Type: application/json' \
-  --data '{"value":"custom"}'
-```
-
-
 <APIRequest
   path="/zones/{zone_id}/settings/{setting_id}"
   method="PATCH"
@@ -72,7 +63,6 @@ If you want to opt a zone out via the API, you can make this API call on or befo
 	}}
 />
 
-
 #### Opt out multiple zones
 
 If you wanted to opt out multiple zones:
diff --git a/src/content/docs/ssl/post-quantum-cryptography/pqc-to-origin.mdx b/src/content/docs/ssl/post-quantum-cryptography/pqc-to-origin.mdx
@@ -36,16 +36,6 @@ It is also possible to opt out of PQC using the same API endpoint.
 This setting affects all outbound connections from the zone you specify in the API call, including `fetch()` requests made by [Workers](/workers/) on your zone.
 :::
 
-```bash
-curl --request PUT \
-"https://api.cloudflare.com/client/v4/zones/{zone_id}/cache/origin_post_quantum_encryption" \
---header "Authorization: Bearer <API_TOKEN>" \
---header "Content-Type: application/json" \
---data '{
-  "value": "<YOUR_CHOSEN_SETTING>"
-}'
-```
-
 <APIRequest
   path="/zones/{zone_id}/cache/origin_post_quantum_encryption"
   method="PUT"
diff --git a/src/content/partials/ssl/forward-client-certificate.mdx b/src/content/partials/ssl/forward-client-certificate.mdx
@@ -19,23 +19,6 @@ This process is only available on accounts with [Cloudflare Access](/cloudflare-
 
 The most common approach to forwarding a certificate is to use the Cloudflare API to [update an mTLS certificate's hostname settings](/api/resources/zero_trust/subresources/access/subresources/certificates/subresources/settings/methods/update/).
 
-```bash title="Request" {11}
-curl --request PUT \
-https://api.cloudflare.com/client/v4/zones/{zone_id}/access/certificates/settings \
---header "X-Auth-Email: <EMAIL>" \
---header "X-Auth-Key: <API_KEY>" \
---header "Content-Type: application/json" \
---data '{
-  "settings": [
-    {
-      "hostname": "<HOSTNAME>",
-      "china_network": false,
-      "client_certificate_forwarding": true
-    }
-  ]
-}'
-```
-
 <APIRequest
   path="/zones/{zone_id}/access/certificates/settings"
   method="PUT"
@@ -53,7 +36,6 @@ https://api.cloudflare.com/client/v4/zones/{zone_id}/access/certificates/setting
 	}}
 />
 
-
 Once `client_certificate_forwarding` is set to `true`, the first request of an mTLS connection will now include the following headers:
 
 * `Cf-Client-Cert-Der-Base64`
