From e84a1a76bf57492858ba1297995389843d47be6c Mon Sep 17 00:00:00 2001 From: s26011-cloud Date: Sun, 23 Aug 2026 15:46:05 +0900 Subject: [PATCH] docs: clarify repetitive "first child of the first child of the root" phrasing The Pitfall in "Preserving and Resetting State" described both Counters' shared position as "the first child of the first child of the root," which reads like an accidental duplicate phrase. Rephrase to name the anchor directly (the
App returns) instead of chaining two "first child of" hops. Fixes #8622 --- src/content/learn/preserving-and-resetting-state.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/learn/preserving-and-resetting-state.md b/src/content/learn/preserving-and-resetting-state.md index 685f63ef4ae..6be57a2b4c3 100644 --- a/src/content/learn/preserving-and-resetting-state.md +++ b/src/content/learn/preserving-and-resetting-state.md @@ -478,7 +478,7 @@ label { You might expect the state to reset when you tick checkbox, but it doesn't! This is because **both of these `` tags are rendered at the same position.** React doesn't know where you place the conditions in your function. All it "sees" is the tree you return. -In both cases, the `App` component returns a `
` with `` as a first child. To React, these two counters have the same "address": the first child of the first child of the root. This is how React matches them up between the previous and next renders, regardless of how you structure your logic. +In both cases, the `App` component returns a `
` with `` as a first child. To React, these two counters have the same "address": they're both the first child of the `
` that `App` returns. This is how React matches them up between the previous and next renders, regardless of how you structure your logic.