From 792c272560d886a663528f20db6d4ebc087dea4b Mon Sep 17 00:00:00 2001 From: Banbarashik <64987973+Banbarashik@users.noreply.github.com> Date: Fri, 11 Aug 2023 18:14:14 +0400 Subject: [PATCH 1/2] docs: fix typo remove misused pronoun "it" --- docs/01-getting-started/03-react-essentials.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/01-getting-started/03-react-essentials.mdx b/docs/01-getting-started/03-react-essentials.mdx index b199d7ba1c864..9010292d513bb 100644 --- a/docs/01-getting-started/03-react-essentials.mdx +++ b/docs/01-getting-started/03-react-essentials.mdx @@ -334,7 +334,7 @@ With this approach, the rendering of `` and ` > - This pattern is **already applied** in [layouts and pages](/docs/app/building-your-application/routing/pages-and-layouts) with the `children` prop so you don't have to create an additional wrapper component. > - Passing React components (JSX) to other components is not a new concept and has always been part of the React composition model. -> - This composition strategy works across Server and Client Components because the component that receives the prop has no knowledge of **what** the prop is. It is only responsible for where the thing that it is passed should be placed. +> - This composition strategy works across Server and Client Components because the component that receives the prop has no knowledge of **what** the prop is. It is only responsible for where the thing that is passed should be placed. > - This allows the passed prop to be rendered independently, in this case, on the server, well before the Client Component is rendered on the client. > - The very same strategy of "lifting content up" has been used to avoid state changes in a parent component re-rendering an imported nested child component. > - You're not limited to the `children` prop. You can use any prop to pass JSX. From fe23e5006f088343c2818f114fd75035ec540cf2 Mon Sep 17 00:00:00 2001 From: JJ Kasper Date: Fri, 11 Aug 2023 14:56:56 -0700 Subject: [PATCH 2/2] Apply suggestions from code review Co-authored-by: Steven --- docs/01-getting-started/03-react-essentials.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/01-getting-started/03-react-essentials.mdx b/docs/01-getting-started/03-react-essentials.mdx index 9010292d513bb..563181c0f74b8 100644 --- a/docs/01-getting-started/03-react-essentials.mdx +++ b/docs/01-getting-started/03-react-essentials.mdx @@ -334,7 +334,7 @@ With this approach, the rendering of `` and ` > - This pattern is **already applied** in [layouts and pages](/docs/app/building-your-application/routing/pages-and-layouts) with the `children` prop so you don't have to create an additional wrapper component. > - Passing React components (JSX) to other components is not a new concept and has always been part of the React composition model. -> - This composition strategy works across Server and Client Components because the component that receives the prop has no knowledge of **what** the prop is. It is only responsible for where the thing that is passed should be placed. +> - This composition strategy works across Server and Client Components because the component that receives the prop can choose where to place the prop, but has no knowledge of **what** the prop is. > - This allows the passed prop to be rendered independently, in this case, on the server, well before the Client Component is rendered on the client. > - The very same strategy of "lifting content up" has been used to avoid state changes in a parent component re-rendering an imported nested child component. > - You're not limited to the `children` prop. You can use any prop to pass JSX.