Fix use of "it's" in docs
Keito Uchiyama committed
Sep 22, 2013 at 13:24 UTC
d262285827d244a058319e9607f63c9e74e9fbb0
2 files changed
+2
-2
docs/_posts/2013-07-17-react-v0-4-0.md
+1
-1
@@ -24,7 +24,7 @@ When you're ready, [go download it](/react/downloads.html)!
24
* Removed `React.autoBind`. [Read our blog post for details...](http://facebook.github.io/react/blog/2013/07/02/react-v0-4-autobind-by-default.html)
25
* Improvements to forms. We've written wrappers around `<input>`, `<textarea>`, `<option>`, and `<select>` in order to standardize many inconsistencies in browser implementations. This includes support for `defaultValue`, and improved implementation of the `onChange` event, and circuit completion. [Read the docs for details...](http://facebook.github.io/react/docs/forms.html)
26
* We've implemented an improved synthetic event system that conforms to the W3C spec.
27
-* Updates to your component are batched now, which may result in a significantly faster re-render of components. `this.setState` now takes an optional callback as it's second parameter. If you were using `onClick={this.setState.bind(this, state)}` previously, you'll want to make sure you add a third parameter so that the event is not treated as the callback.
27
+* Updates to your component are batched now, which may result in a significantly faster re-render of components. `this.setState` now takes an optional callback as its second parameter. If you were using `onClick={this.setState.bind(this, state)}` previously, you'll want to make sure you add a third parameter so that the event is not treated as the callback.
28
29
### JSX
30
docs/docs/07.1-more-about-refs.md
+1
-1
@@ -39,7 +39,7 @@ Consider the case when you wish to tell an `<input />` element (that exists with
39
```
40
41
42
-Notice how, in this example, we want to "tell" the input something - something that it cannot infer from it's props over time. In this case we want to "tell" it that it should now become focused. However, there are some challenges. What is returned from `render()`` is not your actual composition of "child" components, it is merely a *description* of the children at a particular instance in time - a snapshot, if you will.
42
+Notice how, in this example, we want to "tell" the input something - something that it cannot infer from its props over time. In this case we want to "tell" it that it should now become focused. However, there are some challenges. What is returned from `render()`` is not your actual composition of "child" components, it is merely a *description* of the children at a particular instance in time - a snapshot, if you will.
43
44
> Note:
45
>