diff --git a/docs/01-app/02-guides/how-revalidation-works.mdx b/docs/01-app/02-guides/how-revalidation-works.mdx
index 276a23d27689ad..e1052ab20aa027 100644
--- a/docs/01-app/02-guides/how-revalidation-works.mdx
+++ b/docs/01-app/02-guides/how-revalidation-works.mdx
@@ -54,6 +54,8 @@ In the [cache handler API](/docs/app/api-reference/config/next-config-js/cacheHa
 
 ## Multi-Instance Considerations
 
+> **Note:** Revalidation is instance-local by default.
+
 When running multiple Next.js instances behind a load balancer, revalidation events are local by default. Calling `revalidateTag()` on instance A only invalidates the cache on that instance. Other instances continue serving the stale content until they learn about the invalidation.
 
 The cache handler API provides two hooks for distributed coordination: