Move section and update text

Author: pedrosousa

src/content/docs/speed/optimization/content/compression.mdx

@@ -112,6 +112,10 @@ Smaller responses will not be compressed, regardless of their content type.
 
 :::
 
+### Content-Length header handling
+
+When Cloudflare compresses a response sent to the website visitor, it may omit the `Content-Length` HTTP header to avoid delivering incorrect length information caused by dynamic transformations. To preserve the `Content-Length` header set by the origin server, add `cache-control: no-transform` to the origin server's response. This directive prevents Cloudflare from altering compression on responses, allowing the `Content-Length` header to pass through as-is. The `cache-control: no-transform` header must be set by the origin — it cannot be added in client requests.
+
 ---
 
 ## Content compression from origin servers to the Cloudflare network
@@ -151,10 +155,6 @@ If you do not want a particular response from your origin to be encoded with Bro
 Cloudflare will take into consideration the `accept-encoding` header value in website visitors' requests when sending responses to those visitors. However, when requesting content from your origin server, Cloudflare will send a different `Accept-Encoding` header, supporting Brotli and Gzip compression.
 :::
 
-### Content-Length header handling
-
-When Cloudflare compresses a response, it may omit the `Content-Length` HTTP header to avoid delivering incorrect length information caused by dynamic transformations. To preserve the `Content-Length` header, add `cache-control: no-transform` to the origin server's response. This directive prevents Cloudflare from altering compression on responses, allowing the `Content-Length` header to pass through as-is. The `cache-control: no-transform` header must be set by the origin — it cannot be added by client requests.
-
 ---
 
 <Render file="brotli-compression-warning" />