I think the word "root" is misleading here. For me the root implies a single item, and the <li> here is more of a leaf. I think we can avoid all confusion simply by removing the word.
* Update fragments example to use JSX syntax
* Use more standard JSX notation for fragments
* Bring back arrays-based example
* Remove keys in fragment, not needed for static items
* Add note about fragments syntax existing since v16.2
Prevents interpretation as “JSX is closer to JavaScript than HTML is”. The latter is obviously true, but the apparent meaning is the former, which is less obvious.
* Pedantic language change
This page led to the creation of a bad question on a job interview test, leading someone to believe that functions and objects are primitives. They are not.
https://developer.mozilla.org/en-US/docs/Glossary/Primitive
* Verbiage change
* Document how highlight updates works in the optimizing performance page - closes#360
* Change example animated gif to not mention Redux
* Be more explicit about the theory and workflow around using Highlight Updates - closes#360
* improve grammar, correctly label link to #avoid-reconciliation
* Trim content to its essentials and move to a more relevant place in Avoid Reconciliation section - Closes#360
* Make requested changes to wording and host images internally
* Minor rewording
Really enjoyed the newest code-splitting docs!
I caught a minor spelling error: `interuptive` -> `interruptive`. I decided to indulge the writer in myself, and chose to rephrase some things that I thought could be clearer.
That said, I recognize that many of the changes I'm making are subjective. More than happy to simply fix the typo, but I thought I'd submit this to see if others agree with my phrasing changes.
* Init Code-Splitting docs
* Fix <Route path="/"> to use exact
* Fix code splitting typos
* Fix note formatting on the website
* Minor tweaks
De-emphasize webpack, mention Next and Gatsby
