{"patch":"diff --git a\/docs\/cookbook\/cb-03-if-else-in-JSX tip.md b\/docs\/cookbook\/cb-03-if-else-in-JSX tip.md\nindex 219d66c434..c29edf4e90 100644\n--- a\/docs\/cookbook\/cb-03-if-else-in-JSX tip.md\t\n+++ b\/docs\/cookbook\/cb-03-if-else-in-JSX tip.md\t\n@@ -23,8 +23,7 @@ What you're searching for is ternary expression:\n ```js\n \/** @jsx React.DOM *\/\n \n-\/\/ this\n React.renderComponent(

Hello World!<\/div>, mountNode);\n ```\n \n-Try the [JSX compiler](http:\/\/facebook.github.io\/react\/jsx-compiler.html) to see how this works. It's a very simple transformation, thus making JSX entirely optional to use with React.\n+Try the [JSX compiler](http:\/\/facebook.github.io\/react\/jsx-compiler.html).\ndiff --git a\/docs\/cookbook\/cb-03-if-else-in-JSX.md b\/docs\/cookbook\/cb-03-if-else-in-JSX.md\nindex f0146f3131..b1512a6456 100644\n--- a\/docs\/cookbook\/cb-03-if-else-in-JSX.md\n+++ b\/docs\/cookbook\/cb-03-if-else-in-JSX.md\n@@ -6,7 +6,7 @@ permalink: if-else-in-JSX.html\n ---\n \n ### Problem\n-You want to use conditional in JSX.\n+You want to use conditionals in JSX.\n \n ### Solution\n Don't forget that JSX is really just sugar for functions:\n@@ -27,9 +27,8 @@ What you're searching for is ternary expression:\n ```js\n \/** @jsx React.DOM *\/\n \n-\/\/ this\n React.renderComponent(

Hello World!<\/div>, mountNode);\n ```\n \n ### Discussion\n-Try the [JSX compiler](http:\/\/facebook.github.io\/react\/jsx-compiler.html) to see how this works. It's a very simple transformation, thus making JSX entirely optional to use with React.\n+Try the [JSX compiler](http:\/\/facebook.github.io\/react\/jsx-compiler.html).\ndiff --git a\/docs\/cookbook\/cb-04-self-closing-tag tip.md b\/docs\/cookbook\/cb-04-self-closing-tag tip.md\nindex 0a0a7b5422..3f3213122a 100644\n--- a\/docs\/cookbook\/cb-04-self-closing-tag tip.md\t\n+++ b\/docs\/cookbook\/cb-04-self-closing-tag tip.md\t\n@@ -7,4 +7,4 @@ permalink: self-closing-tag-tip.html\n \n In JSX, `` alone is valid while `` isn't.\n \n-Related: every React component can be self-closing where it makes sense: ``.\n+Related: every React component can be self-closing: ``.\ndiff --git a\/docs\/cookbook\/cb-04-self-closing-tag.md b\/docs\/cookbook\/cb-04-self-closing-tag.md\nindex 810a257284..2accb951d1 100644\n--- a\/docs\/cookbook\/cb-04-self-closing-tag.md\n+++ b\/docs\/cookbook\/cb-04-self-closing-tag.md\n@@ -12,4 +12,4 @@ You're getting a parsing error (unexpected token) from JSX.\n One of the reasons might be that you didn't put a `\/` for your self-closing tags. `` is valid while `` isn't.\n \n ### Discussion\n-Every React component can be self-closing where it makes sense: ``.\n+In fact, every React component can be self-closing: ``.\ndiff --git a\/docs\/cookbook\/cb-05-jsx-root-node-count tip.md b\/docs\/cookbook\/cb-05-jsx-root-node-count tip.md\nindex 44e351d414..cb46ec7d5e 100644\n--- a\/docs\/cookbook\/cb-05-jsx-root-node-count tip.md\t\n+++ b\/docs\/cookbook\/cb-05-jsx-root-node-count tip.md\t\n@@ -5,6 +5,6 @@ layout: docs\n permalink: jsx-root-node-count-tip.html\n ---\n \n-Currently in `render`, you can only return one node; if you have, say, a list of `div`s to return, you must wrap your components within, say, one big `div` or `span` (or any other component).\n+Currently, in a component's `render`, you can only return one node; if you have, say, a list of `div`s to return, you must wrap your components within a `div`, `span` or any other component.\n \n-Don't forget that JSX compiles into regular js, and returning two functions doesn't really make syntactic sense.\n+Don't forget that JSX compiles into regular js; returning two functions doesn't really make syntactic sense.\ndiff --git a\/docs\/cookbook\/cb-05-jsx-root-node-count.md b\/docs\/cookbook\/cb-05-jsx-root-node-count.md\nindex d74b02cdca..ab319221ca 100644\n--- a\/docs\/cookbook\/cb-05-jsx-root-node-count.md\n+++ b\/docs\/cookbook\/cb-05-jsx-root-node-count.md\n@@ -9,7 +9,7 @@ permalink: jsx-root-node-count.html\n You're getting a parsing error from JSX.\n \n ### Solution\n-You might have tried to return more than one node from JSX in `render`. Currently, you can only return one node; meaning that you must wrap your components within, say, a `div` or a `span` (or any other component).\n+You might have tried to return more than one node in your component's `render`. Currently, you can only return one node, meaning that you must wrap your components within, say, a `div` or a `span` (or any other component).\n \n ### Discussion\n-Don't forget that JSX compiles into regular js, and returning two functions doesn't really make syntactic sense.\n+Don't forget that JSX compiles into regular js; returning two functions doesn't really make syntactic sense.\ndiff --git a\/docs\/cookbook\/cb-06-style-prop-value-px tip.md b\/docs\/cookbook\/cb-06-style-prop-value-px tip.md\nindex 9f346cad1c..a70f1c6f7b 100644\n--- a\/docs\/cookbook\/cb-06-style-prop-value-px tip.md\t\n+++ b\/docs\/cookbook\/cb-06-style-prop-value-px tip.md\t\n@@ -5,7 +5,7 @@ layout: docs\n permalink: style-prop-value-px-tip.html\n ---\n \n-When specifying a pixel value for your inline `style` prop, React actually automatically appends the string \"px\" for you after your number, so this works:\n+When specifying a pixel value for your inline `style` prop, React automatically appends the string \"px\" for you after your number value, so this works:\n \n ```js\n \/** @jsx React.DOM *\/\n@@ -14,7 +14,7 @@ var divStyle = {height: 10}; \/\/ rendered as \"height:10px\"\n React.renderComponent(

Hello World!<\/div>, mountNode);\n ```\n \n-See [Inline Styles](inline-styles-tip.html) in React for more info.\n+See [Inline Styles](inline-styles-tip.html) for more info.\n \n Sometimes you _do_ want to keep the CSS properties unitless. Here's a list of properties that won't get the automatic \"px\" suffix:\n \ndiff --git a\/docs\/cookbook\/cb-06-style-prop-value-px.md b\/docs\/cookbook\/cb-06-style-prop-value-px.md\nindex 2847d4f0e2..fe5bc9b8b4 100644\n--- a\/docs\/cookbook\/cb-06-style-prop-value-px.md\n+++ b\/docs\/cookbook\/cb-06-style-prop-value-px.md\n@@ -9,7 +9,7 @@ permalink: style-prop-value-px.html\n It's tedious to specify an inline `style` value by appending your number value with the string \"px\" each time.\n \n ### Solution\n-React actually automatically appends the string \"px\" for you after your number, so this works:\n+React automatically appends the string \"px\" for you after your number, so this works:\n \n ```js\n \/** @jsx React.DOM *\/\n@@ -19,7 +19,7 @@ React.renderComponent(

Hello World!<\/div>, mountNode);\n ```\n \n ### Discussion\n-See [Inline Styles](inline-styles.html) in React for more info.\n+See [Inline Styles](inline-styles.html) for more info.\n \n Sometimes you _do_ want to keep the CSS properties unitless. Here's a list of properties that won't get the automatic \"px\" suffix:\n \ndiff --git a\/docs\/cookbook\/cb-07-children-prop-type tip.md b\/docs\/cookbook\/cb-07-children-prop-type tip.md\nindex 0c9e85c00f..107322ab41 100644\n--- a\/docs\/cookbook\/cb-07-children-prop-type tip.md\t\n+++ b\/docs\/cookbook\/cb-07-children-prop-type tip.md\t\n@@ -5,6 +5,6 @@ layout: docs\n permalink: children-prop-type-tip.html\n ---\n \n-Usually, when manipulating a component's children through `this.props.children`, an array is expected. To save an extra array allocation, when `children` only contains one single component, it returns the component itself, without the array wrapper.\n+Usually, a component's `this.props.children` is an array of components. To save an extra array allocation, it returns the component itself when there's only one.\n \n-This means accessing, for example, `this.props.children.length` might be misleading since it could be the length property of a single string component.\n+This means accessing, for example, `this.props.children.length` might be misleading, as it could either be the `length` property of the array of children, or that of a single string component.\ndiff --git a\/docs\/cookbook\/cb-07-children-prop-type.md b\/docs\/cookbook\/cb-07-children-prop-type.md\nindex 8c051f2e47..7097f25ce5 100644\n--- a\/docs\/cookbook\/cb-07-children-prop-type.md\n+++ b\/docs\/cookbook\/cb-07-children-prop-type.md\n@@ -9,6 +9,6 @@ permalink: children-prop-type.html\n You get errors while manipulating `this.props.children` inside a component.\n \n ### Solution\n-Usually, `children` is an array of components. To save an extra array allocation, when it only contains one single component, it returns the component itself.\n+Usually, `children` is an array of components. To save an extra array allocation, it returns the component itself when there's only one.\n \n-This means accessing, for example, `this.props.children.length` might be misleading since it could be the length property of a single string component.\n+This means accessing, for example, `this.props.children.length` might be misleading, as it could either be the `length` property of the array of children, or that of a single string component.\ndiff --git a\/docs\/cookbook\/cb-08-controlled-input-null-value tip.md b\/docs\/cookbook\/cb-08-controlled-input-null-value tip.md\nindex 83b252b1a5..096b35d064 100644\n--- a\/docs\/cookbook\/cb-08-controlled-input-null-value tip.md\t\n+++ b\/docs\/cookbook\/cb-08-controlled-input-null-value tip.md\t\n@@ -5,9 +5,11 @@ layout: docs\n permalink: controlled-input-null-value-tip.html\n ---\n \n-With a controlled input component, specifying a `value` prevents the user from changing the input unless you desire so (more info [here](forms.html)).\n+Specifying the `value` prop on a [controlled component](forms.html) prevents the user from changing the input unless you desire so.\n \n-You might have run into a problem where you specified a `value` but the input can still be changed. In this case, you might have accidentally set your `value` to `undefined` or `null`. The snippet below shows this phenomenon; after a second, the text can be edited.\n+You might have run into a problem where `value` is specified, but the input can still be changed without consent. In this case, you might have accidentally set `value` to `undefined` or `null`.\n+\n+The snippet below shows this phenomenon; after a second, the text becomes editable.\n \n ```js\n \/** @jsx React.DOM *\/\ndiff --git a\/docs\/cookbook\/cb-08-controlled-input-null-value.md b\/docs\/cookbook\/cb-08-controlled-input-null-value.md\nindex 0bcf11c4b7..b928f150a6 100644\n--- a\/docs\/cookbook\/cb-08-controlled-input-null-value.md\n+++ b\/docs\/cookbook\/cb-08-controlled-input-null-value.md\n@@ -9,7 +9,7 @@ permalink: controlled-input-null-value.html\n You specified a `value` parameter for your form input, but the input value can still be modified, contrary to [what you'd expect](forms.html).\n \n ### Solution\n-You might have accidentally set your `value` to `undefined` or `null`. The snippet below shows this phenomenon; after a second, the text can be edited.\n+You might have accidentally set `value` to `undefined` or `null`. The snippet below shows this phenomenon; after a second, the text becomes editable.\n \n ```js\n \/** @jsx React.DOM *\/\ndiff --git a\/docs\/cookbook\/cb-09-componentWillReceiveProps-not-triggered-after-mounting-tip.md b\/docs\/cookbook\/cb-09-componentWillReceiveProps-not-triggered-after-mounting-tip.md\nindex 283cd6fbe0..eb58a304d3 100644\n--- a\/docs\/cookbook\/cb-09-componentWillReceiveProps-not-triggered-after-mounting-tip.md\n+++ b\/docs\/cookbook\/cb-09-componentWillReceiveProps-not-triggered-after-mounting-tip.md\n@@ -7,4 +7,4 @@ permalink: componentWillReceiveProps-not-triggered-after-mounting-tip.html\n \n `componentWillReceiveProps` isn't triggered after the node is put on scene. This is by design. Check out [other lifecycle methods](component-specs.html) for the one that suits your needs.\n \n-The reason for that is because `componentWillReceiveProps` often handles the logic of comparing with the old props and act upon changes; not triggering it at mounting, where there are no old props, clearly defines what the method should do.\n+The reason for that is because `componentWillReceiveProps` often handles the logic of comparing with the old props and acting upon changes; not triggering it at mounting (where there are no old props) helps in defining what the method does.\ndiff --git a\/docs\/cookbook\/cb-09-componentWillReceiveProps-not-triggered-after-mounting.md b\/docs\/cookbook\/cb-09-componentWillReceiveProps-not-triggered-after-mounting.md\nindex c9254504af..d0d9f46633 100644\n--- a\/docs\/cookbook\/cb-09-componentWillReceiveProps-not-triggered-after-mounting.md\n+++ b\/docs\/cookbook\/cb-09-componentWillReceiveProps-not-triggered-after-mounting.md\n@@ -12,4 +12,4 @@ permalink: componentWillReceiveProps-not-triggered-after-mounting.html\n This is by design. Check out [other lifecycle methods](component-specs.html) for the one that suits your needs.\n \n ### Discussion\n-`componentWillReceiveProps` often handles the logic of comparing with the old props and act upon changes; not triggering it at mounting, where there are no old props, clearly defines what the method should do.\n+`componentWillReceiveProps` often handles the logic of comparing with the old props and acting upon changes; not triggering it at mounting (where there are no old props) helps in defining what the method does.\n","files":[{"path":"docs\/cookbook\/cb-03-if-else-in-JSX tip.md","status":"M"},{"path":"docs\/cookbook\/cb-03-if-else-in-JSX.md","status":"M"},{"path":"docs\/cookbook\/cb-04-self-closing-tag tip.md","status":"M"},{"path":"docs\/cookbook\/cb-04-self-closing-tag.md","status":"M"},{"path":"docs\/cookbook\/cb-05-jsx-root-node-count tip.md","status":"M"},{"path":"docs\/cookbook\/cb-05-jsx-root-node-count.md","status":"M"},{"path":"docs\/cookbook\/cb-06-style-prop-value-px tip.md","status":"M"},{"path":"docs\/cookbook\/cb-06-style-prop-value-px.md","status":"M"},{"path":"docs\/cookbook\/cb-07-children-prop-type tip.md","status":"M"},{"path":"docs\/cookbook\/cb-07-children-prop-type.md","status":"M"},{"path":"docs\/cookbook\/cb-08-controlled-input-null-value tip.md","status":"M"},{"path":"docs\/cookbook\/cb-08-controlled-input-null-value.md","status":"M"},{"path":"docs\/cookbook\/cb-09-componentWillReceiveProps-not-triggered-after-mounting-tip.md","status":"M"},{"path":"docs\/cookbook\/cb-09-componentWillReceiveProps-not-triggered-after-mounting.md","status":"M"}],"body":"","parents":["e0df9cbb01aa27953bf074703c6a5de5fc406891"],"commit":{"revision":"fb5f69f44eb6676e9b34f0c62244ad3dc11a3fc5","authorEmail":"chenglou92@gmail.com","authoredAt":"2013-10-06T03:13:17-04:00","authorName":"Cheng Lou","shortRevision":"fb5f69f44e","subject":"modify some wording"}}

dillon1000/react

Files changed