diff --git a/src/content/docs/dns/foundation-dns/setup.mdx b/src/content/docs/dns/foundation-dns/setup.mdx
index 95703d70ee5b16..509142fe01a95f 100644
--- a/src/content/docs/dns/foundation-dns/setup.mdx
+++ b/src/content/docs/dns/foundation-dns/setup.mdx
@@ -16,37 +16,37 @@ To enable advanced nameservers on an existing zone:
 
 1. Opt for advanced nameservers on your zone:
 
-<Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
+    <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain.
-2. Go to **DNS** > **Records**.
-3. In the **Cloudflare nameservers** card, enable **Advanced nameservers**.
-4. After you refresh the page, the card will display the values for your advanced nameservers `NS` records.
+    1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain.
+    2. Go to **DNS** > **Records**.
+    3. In the **Cloudflare nameservers** card, enable **Advanced nameservers**.
+    4. After you refresh the page, the card will display the values for your advanced nameservers `NS` records.
 
-</TabItem> <TabItem label="API">
+    </TabItem> <TabItem label="API">
 
-Use the [Update DNS Settings](/api/operations/dns-settings-for-a-zone-update-dns-settings) endpoint to send a PATCH request like the following:
+    Use the [Update DNS Settings](/api/operations/dns-settings-for-a-zone-update-dns-settings) 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
-}'
-```
+    ```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
+    }'
+    ```
 
-The response body will contain your assigned namservers in the `nameservers` object. You will use these nameservers in the next step.
+    The response body will contain your assigned namservers in the `nameservers` object. You will use these nameservers in the next step.
 
-</TabItem> </Tabs>
+    </TabItem> </Tabs>
 
 2. Update the authoritative nameservers at your registrar. This step depends on whether you are using [Cloudflare Registrar](/registrar/):
    - If you are using Cloudflare Registrar, [contact Cloudflare Support](/support/contacting-cloudflare-support/) to have your nameservers updated.
    - If you are using a different registrar or if your zone is delegated to a parent zone, [manually update your nameservers](/dns/nameservers/update-nameservers/#specific-processes).
 
-:::caution
+      :::caution
 
-Make sure the values for your assigned nameservers are copied exactly.
-:::
+      Make sure the values for your assigned nameservers are copied exactly.
+      :::
diff --git a/src/content/docs/dns/manage-dns-records/reference/dns-record-types.mdx b/src/content/docs/dns/manage-dns-records/reference/dns-record-types.mdx
index 769ba6e0552c78..ceb271853c88a5 100644
--- a/src/content/docs/dns/manage-dns-records/reference/dns-record-types.mdx
+++ b/src/content/docs/dns/manage-dns-records/reference/dns-record-types.mdx
@@ -26,13 +26,13 @@ These records include the following fields:
   * Be 63 characters or less
   * Start with a letter and end with a letter or digit
   * Only contain letters, digits, or hyphens (underscores allowed but discouraged)
-* **IPv4/IPv6 address**: Your origin server address (cannot be a [Cloudflare IP](https://www.cloudflare.com/ips)) 
+* **IPv4/IPv6 address**: Your origin server address (cannot be a [Cloudflare IP](https://www.cloudflare.com/ips))
 
   :::note
 
   Cloudflare uses the [canonical notation](https://www.rfc-editor.org/rfc/rfc5952.html#section-4.2) to store DNS records. This means that an `AAAA` record with content `fe80::0:0:1` is stored and returned as `fe80::1`, for example.
 
-  Alternative notations of IPv4 addresses (`1.1` for `1.0.0.1`, for example) are not supported for `A` records. 
+  Alternative notations of IPv4 addresses (`1.1` for `1.0.0.1`, for example) are not supported for `A` records.
   :::
 
 * **TTL**: Time to live, which controls how long DNS resolvers should cache a response before revalidating it.
@@ -337,3 +337,7 @@ You only need to add NS records when you are [creating custom or vanity nameserv
 Most Cloudflare domains do not need to add these records and should instead follow our [DNSSEC setup guide](/dns/dnssec/).
 
 <Render file="api-field-definitions" />
+
+### Other
+
+Cloudflare also supports other record types that are less common, such as URI, NAPTR, and certificate-related record types (SSHFP, TLSA, SMIMEA, and CERT). Refer to our [blog post](https://blog.cloudflare.com/additional-record-types-available-with-cloudflare-dns/) for more information.
\ No newline at end of file