Resetting state docs improvement

Inizia dalla sezione collegata «Option 1: Rendering a component in different positions» e rivedi il relativo diagramma e la spiegazione dei figli condizionali. Confronta la formulazione con il modo in cui React tratta i false children e le posizioni nell’albero. Il lavoro è completato quando il diagramma e il testo spiegano accuratamente i tre casi senza implicare che la posizione visiva a sinistra o a destra definisca l’identità di un figlio.

Over here: https://react.dev/learn/preserving-and-resetting-state#option-1-rendering-a-component-in-different-positions
about resetting a state, just because a line is drawn to the right, now the Counter becomes a "right" child?

And then, just because the line is drawn to the left, now the Counter becomes a "left" child?

The diagram is:

In reality, it is just "children" nodes. So if you have one child with a line drawn to the left, it doesn't make it a "left" child.

Likewise, if you have one child with a line drawn to the right, it doesn't make it a "right" child.

To some degree, it dumbs down the programmers.

The truth is:

For those three situations in the diagram:

1. First child is Counter, and second child is false. (isPlayerA && whatever becomes false if isPlayer is false). There should be a solid line going to a false as a second child.
2. First child is false, and second child is Counter. There should be a solid line going down to the first child which is false.
3. The third case is just like (1).

And then, the rule of React is, the false will not be rendered. But the tree in fact has a false, for the "tree structure" to be "different".

If I am not mistaken, this "tree" is composed, and compared to the previous "tree", for React to decide whether to change something in the actual DOM. This "current" tree and "previous tree", is the idea of Virtual DOM.

So the concepts should be set straight here.