From 141672cc29465e2c717296cc068becb0328582a4 Mon Sep 17 00:00:00 2001 From: nauvalazhar Date: Tue, 20 Aug 2024 21:34:34 +0700 Subject: [PATCH] docs: adding a space after the period --- docs/02-app/01-building-your-application/04-caching/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/02-app/01-building-your-application/04-caching/index.mdx b/docs/02-app/01-building-your-application/04-caching/index.mdx index fa203143acb29..566dff34689f2 100644 --- a/docs/02-app/01-building-your-application/04-caching/index.mdx +++ b/docs/02-app/01-building-your-application/04-caching/index.mdx @@ -318,7 +318,7 @@ You can opt out of the Full Route Cache, or in other words, dynamically render c Next.js has an in-memory client-side router cache that stores the RSC payload of route segments, split by layouts, loading states, and pages. -When a user navigates between routes, Next.js caches the visited route segments and [prefetches](/docs/app/building-your-application/routing/linking-and-navigating#2-prefetching) the routes the user is likely to navigate to.This results in instant back/forward navigation, no full-page reload between navigations, and preservation of React state and browser state. +When a user navigates between routes, Next.js caches the visited route segments and [prefetches](/docs/app/building-your-application/routing/linking-and-navigating#2-prefetching) the routes the user is likely to navigate to. This results in instant back/forward navigation, no full-page reload between navigations, and preservation of React state and browser state. With the Router Cache: