diff --git a/src/content/docs/data-localization/metadata-boundary/faq.mdx b/src/content/docs/data-localization/metadata-boundary/faq.mdx
index 29d1b1335e95324..9c0fc874b4283e9 100644
--- a/src/content/docs/data-localization/metadata-boundary/faq.mdx
+++ b/src/content/docs/data-localization/metadata-boundary/faq.mdx
@@ -6,6 +6,7 @@ sidebar:
   order: 3
 description: Commonly asked questions about Cloudflare's Customer Metadata Boundary.
 ---
+
 ## What data is covered by the Customer Metadata Boundary?
 
 Nearly all end user metadata is covered by the Customer Metadata Boundary. This includes all of the end user data for which Cloudflare is a processor, as defined in the [Cloudflare Privacy Policy](https://www.cloudflare.com/privacypolicy/). Cloudflare is a data processor of Customer Logs, which are defined as end user logs that we make available to our customers via the dashboard or other online interfaces. End users are those who access or use our customers' domains, networks, websites, application programming interfaces, and applications.
diff --git a/src/content/docs/speed/optimization/content/compression.mdx b/src/content/docs/speed/optimization/content/compression.mdx
index 5921dc0d60f6a4c..3db0908bccd8f37 100644
--- a/src/content/docs/speed/optimization/content/compression.mdx
+++ b/src/content/docs/speed/optimization/content/compression.mdx
@@ -12,6 +12,7 @@ head:
 import { Render } from "~/components";
 
 Cloudflare compresses content in two ways: between Cloudflare and your website visitors and between Cloudflare and your origin server.
+
 ## Compression between Cloudflare and website visitors
 
 In addition to Cloudflare's [default caching behavior](/cache/concepts/default-cache-behavior/), Cloudflare supports Gzip, Brotli, and Zstandard compression when delivering content to website visitors.