Skip to content

Commit d285c87

Browse files
Update docs/pages/docs/routing/middleware.mdx
Co-authored-by: Jan Amann <jan@amann.work>
1 parent 6714828 commit d285c87

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/pages/docs/routing/middleware.mdx

+1-1
Original file line numberDiff line numberDiff line change
@@ -346,7 +346,7 @@ export default createMiddleware({
346346
<details>
347347
<summary>How to revalidate localized pathnames?</summary>
348348

349-
Depending on how the route is generated, whether statically or dynamically, if you're attempting to use Next.js's function `revalidatePath()`, you will need to call it with two different pathnames.
349+
Depending on if a route is generated statically (at build time) or dynamically (at runtime), [`revalidatePath`](https://nextjs.org/docs/app/api-reference/functions/revalidatePath) needs to be called either for the localized or the internal pathname.
350350

351351
Let's take an example with this folder structure:
352352
```

0 commit comments

Comments
 (0)