From 514ad65330f36492c6638d090e67cfaf3408bae1 Mon Sep 17 00:00:00 2001
From: Saurabh <79586784+m4saurabh@users.noreply.github.com>
Date: Thu, 7 May 2026 11:46:29 +0530
Subject: [PATCH] docs: update to caching.mdx to be more explicit

---
 pages/cloudflare/caching.mdx | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/pages/cloudflare/caching.mdx b/pages/cloudflare/caching.mdx
index 2009bd8..06191da 100644
--- a/pages/cloudflare/caching.mdx
+++ b/pages/cloudflare/caching.mdx
@@ -3,6 +3,11 @@ import { Tabs } from "nextra/components";
 
 ## Caching
 
+<Callout type="info">
+  Everything in this page only concerns SSG/ISR and the data cache, SSR route will work out of the box without
+  any caching config.
+</Callout>
+
 Next.js offers multiple ways to improve an application's performance by [caching](https://nextjs.org/docs/app/building-your-application/data-fetching/fetching-caching-and-revalidating#caching-data) routes and network requests. An application will try to pre-render and cache as much data as possible during build-time to reduce the amount of work required when serving a response to a user.
 
 The cache data are updated using revalidation, either periodically or on-demand:
@@ -26,11 +31,6 @@ The adapter provides several implementations for each of those components config
 
 This guide provides guidelines for common use cases before detailing all the configuration options.
 
-<Callout type="info">
-  Everything in this page only concerns SSG/ISR and the data cache, SSR route will work out of the box without
-  any caching config.
-</Callout>
-
 ### Guidelines
 
 #### Small site using revalidation