* 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
* Break out Installation into top-level doc section
* Update navigation (prev/next, nav tree)
- Move Installation section to top
- Add next/prev to install pages
* add links to other install options from try react page
* fix markdown link
* Clarify that Quick Start and Install are optional "next steps"
* Add top-level CDN page
This is useful for Codepen and other Unpkg-y setups
* Add link to Tutorial from Try React
* Update CRA link in tutorial
* Make Try React subheader a proper sentence
* Add "minimal"
* Explain local dev setup is more work than Codepen etc
* Fix typos
* Add : between headings
* add note that CRA is not lightweight
* fix typo
* Update add-react-to-a-new-app.md
* Update add-react-to-a-new-app.md
* Remove the Bower note
* Update try-react.md
* Tweak wording
* Use direct link
Maybe I'm somehow weird, but I lived for some time with an idea that `React.Component` does implement `shouldComponentUpdate` with deep comparison. `React.PureComponent` is faster because it compares shallowly.
The changes I propose should avoid this "implicit" kind of way of thinking, since it would explicitly state that `React.Component` does not compare anything.
