diff --git a/src/content/docs/cache/concepts/cache-behavior.mdx b/src/content/docs/cache/concepts/cache-behavior.mdx
index 2ed212b0dbeb784..cdab724ddc686c7 100644
--- a/src/content/docs/cache/concepts/cache-behavior.mdx
+++ b/src/content/docs/cache/concepts/cache-behavior.mdx
@@ -19,7 +19,7 @@ When you make a `HEAD` request for a cacheable resource and Cloudflare does not
 
 For non-cacheable requests, `Set-Cookie` is always preserved. For cacheable requests, there are three possible behaviors:
 
-* `Set-Cookie` is returned from origin and the default cache level is used. If origin cache control is not enabled, Cloudflare removes the `Set-Cookie` and caches the asset. If origin cache control is enabled, Cloudflare does not cache the asset and preserves the `Set-Cookie`. A cache status of BYPASS is returned.
+* `Set-Cookie` is returned from origin and the default cache level is used. If [origin cache control](/cache/concepts/cache-control/) is not enabled, Cloudflare removes the `Set-Cookie` and caches the asset. If origin cache control is enabled, Cloudflare does not cache the asset and preserves the `Set-Cookie`. A cache status of `BYPASS` is returned.
 
 * `Set-Cookie` is returned from origin and the cache level is set to `Cache Everything` in Page Rules, or `Eligible for cache` in Cache Rules. In this case, Cloudflare preserves the `Set-Cookie` but does not cache the asset. A cache `MISS` will be returned every time.