From 3da768f839b69c498def4a16f1df582c57d54ef3 Mon Sep 17 00:00:00 2001 From: Simon Gavelin Date: Thu, 25 Aug 2022 16:21:39 +0200 Subject: [PATCH] [docs] Fixed 404 links to Layouts RFC blog post (#39937) Fixes broken links to Next.js Router and Layouts RFC blog post ## Documentation / Examples - [x] Make sure the linting passes by running `pnpm lint` --- docs/advanced-features/react-18/server-components.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/advanced-features/react-18/server-components.md b/docs/advanced-features/react-18/server-components.md index 839bda3274a3..906dab699bff 100644 --- a/docs/advanced-features/react-18/server-components.md +++ b/docs/advanced-features/react-18/server-components.md @@ -4,7 +4,7 @@ Server Components allow us to render React components on the server. This is fun ### Next Router and Layouts RFC -We are currently implementing the [Next.js Router and Layouts RFC](/blog/layouts-rfc). +We are currently implementing the [Next.js Router and Layouts RFC](https://nextjs.org/blog/layouts-rfc). The new Next.js router will be built on top of React 18 features, including React Server Components. @@ -12,7 +12,7 @@ One of the biggest proposed changes is that, by default, files inside a new `app This will allow you to automatically adopt React Server Components when migrating from `pages` to `app`. -You can find more information on the [RFC](/blog/layouts-rfc) and we welcome your feedback on [Github Discussions](https://github.com/vercel/next.js/discussions/37136). +You can find more information on the [RFC](https://nextjs.org/blog/layouts-rfc) and we welcome your feedback on [Github Discussions](https://github.com/vercel/next.js/discussions/37136). ### Server Components Conventions