- you can _just_ open it in
- It _renders_ a heading saying “Hello, world!” on the page. - you are using the same word as the thing you are describing.
- “A Note on JavaScript” the title doe snot suggest that you need to read it because you are learning about react ,not JS. Something like “React & JavaScript” or something like “Knowledge Level Assumptions”
- “we recommend **refreshing** your JavaScript knowledge so you can follow along more easily.” — refreshing suggest that someone. Already knows JS, so if they don’t know JS they will feel dejected. Try “We highly recommend [going through a Javascript tutorial]() to check your knowledge level.”
- “We also use some of the ES6 syntax” - **We** that suggests its a us vs the user. Instead go for “**The documentation** will use some [ES6 Syntax](LINK TO WHAT IS ES6)”
It's obvious enough that this is the same method. I don't think repeating its name in the list brings any value, and it puts too much visual emphasis on something we're trying to deemphasize.
Correct a typo in the render method comments for the "CustomTextInput" component of the "Adding a Ref to a DOM Element" example. The first line of the comments reads "tell React that we want the associate the <input> ref". The word "the" should be "to" resulting in the comment "tell React that we want to associate the <input> ref".
* Add 'visual components' use case for forwarding refs
* Rearrange "forwarding refs" to focus on simple use case
* Minor wording nits to 2018-03-29-react-v-16-3.md
* Minor wording nits to forwarding-refs.md
* Add more info to the forwardRef reference doc
* Minor wording nits to reference-react.md
* Added an example showing how to update the context from inside a (deeply) nested component
* Wrap comments
* Wrap comments
* Tweak wording
* Prettier
* Prettier
* Typo: "funtion" -> "function"