Remove original bash code blocks

Author: RebeccaTamachiro

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/domain-support/custom-metadata.mdx

@@ -32,24 +32,6 @@ Please speak with your Solutions Engineer to discuss additional logic and requir
 
 You may add custom metadata to Cloudflare via the Custom Hostnames API. This data can be added via a [`PATCH` request](/api/resources/custom_hostnames/methods/edit/) to the specific hostname ID to set metadata for that hostname, for example:
 
-```bash
-curl --request PATCH \
-"https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames/{hostname_id}" \
---header "X-Auth-Email: <EMAIL>" \
---header "X-Auth-Key: <API_KEY>" \
---header "Content-Type: application/json" \
---data '{
-  "ssl": {
-    "method": "http",
-    "type": "dv"
-  },
-  "custom_metadata": {
-    "customer_id": "12345",
-    "redirect_to_https": true,
-    "security_tag": "low"
-  }
-}'
-```
 
 <APIRequest
   path="/zones/{zone_id}/custom_hostnames/{custom_hostname_id}"

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/performance/early-hints-for-saas.mdx

@@ -26,28 +26,6 @@ Before you can employ Early Hints for SaaS, you need to create a custom hostname
 
 3. If you are [creating a new custom hostname](/api/resources/custom_hostnames/methods/create/), make an API call such as the example below, specifying `"early_hints": "on"`:
 
-```bash
-curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames" \
---header "X-Auth-Email: <EMAIL>" \
---header "X-Auth-Key: <API_KEY>" \
---header "Content-Type: application/json" \
---data '{
-  "hostname": "{hostname}",
-  "ssl": {
-    "method": "http",
-    "type": "dv",
-    "settings": {
-      "http2": "on",
-      "min_tls_version": "1.2",
-      "tls_1_3": "on",
-      "early_hints": "on"
-    },
-    "bundle_method": "ubiquitous",
-    "wildcard": false
-  }
-}'
-```
-
 <APIRequest
   path="/zones/{zone_id}/custom_hostnames"
   method="POST"
@@ -70,12 +48,6 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames" \
 
 4. For an existing custom hostname, locate the `id` of that hostname via a `GET` call:
 
-```bash
-curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames?hostname={hostname}" \
---header "X-Auth-Email: <EMAIL>" \
---header "X-Auth-Key: <API_KEY>"
-```
-
 <APIRequest
   path="/zones/{zone_id}/custom_hostnames"
   method="GET"
@@ -86,26 +58,6 @@ curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames?host
 
 5. Then make an API call such as the example below, specifying `"early_hints": "on"`:
 
-```bash
-curl --request PATCH \
-"https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames/{id}" \
---header "X-Auth-Email: <EMAIL>" \
---header "X-Auth-Key: <API_KEY>" \
---header "Content-Type: application/json" \
---data '{
-  "ssl": {
-    "method": "http",
-    "type": "dv",
-    "settings": {
-      "http2": "on", // Note: These settings will be set to default if not included when updating early hints
-      "min_tls_version": "1.2",
-      "tls_1_3": "on",
-      "early_hints": "on"
-    }
-  }
-}'
-```
-
 <APIRequest
   path="/zones/{zone_id}/custom_hostnames/{custom_hostname_id}"
   method="PATCH"

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/security/waf-for-saas/index.mdx

@@ -20,14 +20,6 @@ Before you can use WAF for SaaS, you need to create a custom hostname. Review [G
 
 You can also create a custom hostname through the API:
 
-```bash
-curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames" \
---header "X-Auth-Email: <EMAIL>" \
---header "X-Auth-Key: <API_KEY>" \
---header "Content-Type: application/json" \
---data '{"Hostname":"example.com"}, "Ssl":{wildcard:false}}'
-```
-
 <APIRequest
   path="/zones/{zone_id}/custom_hostnames"
   method="POST"
@@ -49,12 +41,6 @@ To apply WAF to your custom hostname, you need to create an association between
 
 3. Locate your custom hostname ID by making a `GET` call in the API:
 
-```bash
-curl "https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames" \
---header "X-Auth-Email: <EMAIL>" \
---header "X-Auth-Key: <API_KEY>"
-```
-
 <APIRequest
   path="/zones/{zone_id}/custom_hostnames"
   method="GET"
@@ -70,20 +56,6 @@ One instance of low, medium, and high rules could be rate limiting. You can spec
 
 5. Make an API call in the format below using your Cloudflare email and the IDs gathered above:
 
-```bash
-curl --request PATCH \
-"https://api.cloudflare.com/client/v4/zones/{zone_id}/custom_hostnames/{custom_hostname_id}" \
---header "X-Auth-Email: <EMAIL>"
---header "X-Auth-Key: <API_KEY>" \
---header "Content-Type: application/json" \
---data '{
-  "custom_metadata": {
-    "customer_id": "12345",
-    "security_level": "low"
-  }
-}'
-```
-
 <APIRequest
   path="/zones/{zone_id}/custom_hostnames/{custom_hostname_id}"
   method="PATCH"
@@ -103,30 +75,6 @@ This assigns custom metadata to your custom hostname so that it has a security t
 
 2. Build your rules either [through the dashboard](/waf/custom-rules/create-dashboard/) or via the API. An example rate limiting rule, corresponding to `"security_level"` low, is shown below as an API call.
 
-```bash
-curl --request PUT \
-"https://api.cloudflare.com/client/v4/zones/{zone_id}/rulesets/phases/http_ratelimit/entrypoint" \
---header "Authorization: Bearer <API_TOKEN>" \
---header "Content-Type: application/json" \
---data '{
-  "rules": [
-    {
-      "action": "block",
-      "ratelimit": {
-        "characteristics": [
-          "cf.colo.id",
-          "ip.src"
-        ],
-        "period": 10,
-        "requests_per_period": 2,
-        "mitigation_timeout": 60
-      },
-      "expression": "lookup_json_string(cf.hostname.metadata, \"security_level\") eq \"low\" and http.request.uri contains \"login\""
-    }
-  ]
-}'
-```
-
 <APIRequest
   path="/zones/{zone_id}/rulesets/phases/{ruleset_phase}/entrypoint"
   method="PUT"