{"parents":["9698b54dfe22d7ec7201ba2b9095ae382f7119bd"],"body":"Closes #1859.","commit":{"authorEmail":"james.seppi@gmail.com","subject":"fix typo","authorName":"James Seppi","authoredAt":"2014-07-17T16:23:07-05:00","revision":"6d1ede34df619f3dbb1ec139450733095d8abbcf","shortRevision":"6d1ede34df"},"files":[{"status":"M","path":"docs\/_posts\/2014-07-13-react-v0.11-rc1.md"},{"status":"M","path":"docs\/_posts\/2014-07-17-react-v0.11.md"}],"patch":"diff --git a\/docs\/_posts\/2014-07-13-react-v0.11-rc1.md b\/docs\/_posts\/2014-07-13-react-v0.11-rc1.md\nindex 9f300a9f95..17417196a6 100644\n--- a\/docs\/_posts\/2014-07-13-react-v0.11-rc1.md\n+++ b\/docs\/_posts\/2014-07-13-react-v0.11-rc1.md\n@@ -29,7 +29,7 @@ Starting in React 0.11, `getDefaultProps()` is called only once when `React.crea\n \n ## Rendering to `null`\n \n-Since React's release, people have been using work arounds to \"render nothing\". Usually this means returning an empty `` or ``. Some people even got clever and started returning `` to avoid extraneous DOM nodes. We finally provided a \"blessed\" solution that allows developers to writing meaningful code. Returning `null` in an explicit indication to React that you do not want anything rendered. Behind the scenes we make this work with a `

` elements do not affect layout in any way, so you can feel safe using `null` today!\n+Since React's release, people have been using work arounds to \"render nothing\". Usually this means returning an empty `<div\/>` or `<span\/>`. Some people even got clever and started returning `<noscript\/>` to avoid extraneous DOM nodes. We finally provided a \"blessed\" solution that allows developers to write meaningful code. Returning `null` is an explicit indication to React that you do not want anything rendered. Behind the scenes we make this work with a `<noscript>` element, though in the future we hope to not put anything in the document. In the mean time, `<noscript>` elements do not affect layout in any way, so you can feel safe using `null` today!\n \n ```js\n \/\/ Before\ndiff --git a\/docs\/_posts\/2014-07-17-react-v0.11.md b\/docs\/_posts\/2014-07-17-react-v0.11.md\nindex 802cbd0798..939092084b 100644\n--- a\/docs\/_posts\/2014-07-17-react-v0.11.md\n+++ b\/docs\/_posts\/2014-07-17-react-v0.11.md\n@@ -32,7 +32,7 @@ Starting in React 0.11, `getDefaultProps()` is called only once when `React.crea\n \n ## Rendering to `null`\n \n-Since React's release, people have been using work arounds to \"render nothing\". Usually this means returning an empty `<div\/>` or `<span\/>`. Some people even got clever and started returning `<noscript\/>` to avoid extraneous DOM nodes. We finally provided a \"blessed\" solution that allows developers to writing meaningful code. Returning `null` in an explicit indication to React that you do not want anything rendered. Behind the scenes we make this work with a `<noscript>` element, though in the future we hope to not put anything in the document. In the mean time, `<noscript>` elements do not affect layout in any way, so you can feel safe using `null` today!\n+Since React's release, people have been using work arounds to \"render nothing\". Usually this means returning an empty `<div\/>` or `<span\/>`. Some people even got clever and started returning `<noscript\/>` to avoid extraneous DOM nodes. We finally provided a \"blessed\" solution that allows developers to write meaningful code. Returning `null` is an explicit indication to React that you do not want anything rendered. Behind the scenes we make this work with a `<noscript>` element, though in the future we hope to not put anything in the document. In the mean time, `<noscript>` elements do not affect layout in any way, so you can feel safe using `null` today!\n \n ```js\n \/\/ Before\n"}</article></body></html>

dillon1000/react

Files changed