diff --git a/src/content/docs/network/response-buffering.mdx b/src/content/docs/network/response-buffering.mdx
index 762c5f774ca40d6..9a7d2cee10ca74b 100644
--- a/src/content/docs/network/response-buffering.mdx
+++ b/src/content/docs/network/response-buffering.mdx
@@ -14,7 +14,7 @@ If your domain sends many small packets, it may be faster to buffer the file and
 
 ## How it works
 
-By default, Cloudflare **streams** traffic data, meaning that each packet is sent as it becomes available. This can improve the delivery of large files. However, this streaming behavior only applies to dynamic traffic; cacheable traffic is buffered and this behavior cannot be changed.
+By default, Cloudflare **streams** traffic data, meaning that each packet is sent as it becomes available. This can improve the delivery of large files. However, this streaming behavior only applies to dynamic traffic; cacheable traffic (that is, **any** status noted in [Cloudflare cache responses](https://developers.cloudflare.com/cache/concepts/cache-responses/) with the exception of **DYNAMIC**) is buffered and this behavior cannot be changed.
 
 If your domain sends many small packets, however, it might be faster to **buffer** the file. This approach waits to send the full file until all packets are ready, preventing a client browser from having to re-assemble packets.