From 6aeb8b21fddb8a54a3ded4aa046559faa6be9090 Mon Sep 17 00:00:00 2001 From: shehroze-1122 Date: Sat, 11 Jan 2025 20:26:32 +0100 Subject: [PATCH] Docs: fix the misstatement in full route cache invalidation section --- docs/01-app/03-building-your-application/04-caching/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/01-app/03-building-your-application/04-caching/index.mdx b/docs/01-app/03-building-your-application/04-caching/index.mdx index 434357efa6e67..4772a7541006a 100644 --- a/docs/01-app/03-building-your-application/04-caching/index.mdx +++ b/docs/01-app/03-building-your-application/04-caching/index.mdx @@ -299,7 +299,7 @@ By default, the Full Route Cache is persistent. This means that the render outpu There are two ways you can invalidate the Full Route Cache: -- **[Revalidating Data](/docs/app/building-your-application/caching#revalidating)**: Revalidating the [Data Cache](#data-cache), will in turn invalidate the Router Cache by re-rendering components on the server and caching the new render output. +- **[Revalidating Data](/docs/app/building-your-application/caching#revalidating)**: Revalidating the [Data Cache](#data-cache), will in turn invalidate the Full Route Cache by re-rendering components on the server and caching the new render output. - **Redeploying**: Unlike the Data Cache, which persists across deployments, the Full Route Cache is cleared on new deployments. ### Opting out