Hello World!<\/div>, mountNode);\n-```\n-\n-Style keys are camelCased in order to be consistent with accessing the properties using node.style.___ in DOM. This also explains why WebkitTransition has an uppercase \"W\".\ndiff --git a\/docs\/cookbook\/02-inline-styles.md b\/docs\/cookbook\/02-inline-styles.md\nindex 9f32333000..cd33234764 100644\n--- a\/docs\/cookbook\/02-inline-styles.md\n+++ b\/docs\/cookbook\/02-inline-styles.md\n@@ -7,11 +7,7 @@ next: if-else-in-JSX.html\n prev: introduction.html\n ---\n \n-### Problem\n-You want to apply inline style to an element.\n-\n-### Solution\n-Instead of writing a string, create an object whose key is the camelCased version of the style name, and whose value is the style's value, in string:\n+In React, inline styles are not specified as a string, but as an object whose key is the camelCased version of the style name, and whose value is the style's value in string:\n \n ```js\n \/** @jsx React.DOM *\/\n@@ -25,5 +21,4 @@ var divStyle = {\n React.renderComponent(

Hello World!<\/div>, mountNode);\n ```\n \n-### Discussion\n-Style keys are camelCased in order to be consistent with accessing the properties using `node.style.___` in DOM. This also explains why `WebkitTransition` has an uppercase \"W\".\n+Style keys are camelCased in order to be consistent with accessing the properties using node.style.___ in DOM. This also explains why WebkitTransition has an uppercase \"W\".\ndiff --git a\/docs\/cookbook\/03-if-else-in-JSX tip.md b\/docs\/cookbook\/03-if-else-in-JSX tip.md\ndeleted file mode 100644\nindex 24ecfb6a83..0000000000\n--- a\/docs\/cookbook\/03-if-else-in-JSX tip.md\t\n+++ \/dev\/null\n@@ -1,31 +0,0 @@\n----\n-id: if-else-in-JSX-tip\n-title: If-Else in JSX\n-layout: cookbook\n-permalink: if-else-in-JSX-tip.html\n-prev: inline-styles.html\n-next: self-closing-tag.html\n----\n-\n-`if-else` statements don't work inside JSX, since JSX is really just sugar for functions:\n-\n-```js\n-\/** @jsx React.DOM *\/\n-\n-\/\/ this\n-React.renderComponent(

Hello World!<\/div>, mountNode);\n-\/\/ is the same as this\n-React.renderComponent(React.DOM.div({id:\"msg\"}, \"Hello World!\"), mountNode);\n-```\n-\n-Which means `

Hello World!<\/div>` doesn't make sense, as (if it worked) it would be compiled down to something like this `React.DOM.div({id: if (true){ 'msg' }}, \"Hello World!\")`, which isn't valid JS.\n-\n-What you're searching for is ternary expression:\n-\n-```js\n-\/** @jsx React.DOM *\/\n-\n-React.renderComponent(

Hello World!<\/div>, mountNode);\n-```\n-\n-Try the [JSX compiler](\/react\/jsx-compiler.html).\ndiff --git a\/docs\/cookbook\/03-if-else-in-JSX.md b\/docs\/cookbook\/03-if-else-in-JSX.md\nindex 089184db2c..a94d9ae473 100644\n--- a\/docs\/cookbook\/03-if-else-in-JSX.md\n+++ b\/docs\/cookbook\/03-if-else-in-JSX.md\n@@ -7,11 +7,7 @@ prev: inline-styles.html\n next: self-closing-tag.html\n ---\n \n-### Problem\n-You want to use conditionals in JSX.\n-\n-### Solution\n-Don't forget that JSX is really just sugar for functions:\n+`if-else` statements don't work inside JSX, since JSX is really just sugar for functions:\n \n ```js\n \/** @jsx React.DOM *\/\n@@ -32,5 +28,4 @@ What you're searching for is ternary expression:\n React.renderComponent(

Hello World!<\/div>, mountNode);\n ```\n \n-### Discussion\n-Try the [JSX compiler](react\/jsx-compiler.html).\n+Try the [JSX compiler](\/react\/jsx-compiler.html).\ndiff --git a\/docs\/cookbook\/04-self-closing-tag tip.md b\/docs\/cookbook\/04-self-closing-tag tip.md\ndeleted file mode 100644\nindex ff47be3b79..0000000000\n--- a\/docs\/cookbook\/04-self-closing-tag tip.md\t\n+++ \/dev\/null\n@@ -1,12 +0,0 @@\n----\n-id: self-closing-tag-tip\n-title: Self-Closing Tag\n-layout: cookbook\n-permalink: self-closing-tag-tip.html\n-prev: if-else-in-JSX.html\n-next: jsx-root-node-count.html\n----\n-\n-In JSX, `` alone is valid while `` isn't.\n-\n-Related: every React component can be self-closing: ``.\ndiff --git a\/docs\/cookbook\/04-self-closing-tag.md b\/docs\/cookbook\/04-self-closing-tag.md\nindex bfb8c346cc..3fdba6f960 100644\n--- a\/docs\/cookbook\/04-self-closing-tag.md\n+++ b\/docs\/cookbook\/04-self-closing-tag.md\n@@ -7,11 +7,6 @@ prev: if-else-in-JSX.html\n next: jsx-root-node-count.html\n ---\n \n-### Problem\n-You're getting a parsing error (unexpected token) from JSX.\n+In JSX, `` alone is valid while `` isn't.\n \n-### Solution\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-In fact, every React component can be self-closing: ``.\n+Related: every React component can be self-closing: ``.\ndiff --git a\/docs\/cookbook\/05-jsx-root-node-count tip.md b\/docs\/cookbook\/05-jsx-root-node-count tip.md\ndeleted file mode 100644\nindex 814ae94393..0000000000\n--- a\/docs\/cookbook\/05-jsx-root-node-count tip.md\t\n+++ \/dev\/null\n@@ -1,12 +0,0 @@\n----\n-id: jsx-root-node-count-tip\n-title: Maximum number of JSX root nodes\n-layout: cookbook\n-permalink: jsx-root-node-count-tip.html\n-prev: self-closing-tag.html\n-next: style-prop-value-px.html\n----\n-\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; returning two functions doesn't really make syntactic sense. Likewise, don't put more than one child in a ternary.\ndiff --git a\/docs\/cookbook\/05-jsx-root-node-count.md b\/docs\/cookbook\/05-jsx-root-node-count.md\nindex dd0fd8cef0..10f9ab06cf 100644\n--- a\/docs\/cookbook\/05-jsx-root-node-count.md\n+++ b\/docs\/cookbook\/05-jsx-root-node-count.md\n@@ -7,11 +7,6 @@ prev: self-closing-tag.html\n next: style-prop-value-px.html\n ---\n \n-### Problem\n-You're getting a parsing error from JSX.\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-### Solution\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; returning two functions doesn't really make syntactic sense. Likewise, don't put more than one child in a ternary.\ndiff --git a\/docs\/cookbook\/06-style-prop-value-px tip.md b\/docs\/cookbook\/06-style-prop-value-px tip.md\ndeleted file mode 100644\nindex 6ef2b3eeb7..0000000000\n--- a\/docs\/cookbook\/06-style-prop-value-px tip.md\t\n+++ \/dev\/null\n@@ -1,29 +0,0 @@\n----\n-id: style-prop-value-px-tip\n-title: Shorthand for specifying pixel values in style prop\n-layout: cookbook\n-permalink: style-prop-value-px-tip.html\n-prev: jsx-root-node-count.html\n-next: children-prop-type.html\n----\n-\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-\n-var divStyle = {height: 10}; \/\/ rendered as \"height:10px\"\n-React.renderComponent(

Hello World!<\/div>, mountNode);\n-```\n-\n-See [Inline Styles](\/react\/docs\/cookbook\/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-\n-- fillOpacity\n-- fontWeight\n-- lineHeight\n-- opacity\n-- orphans\n-- zIndex\n-- zoom\ndiff --git a\/docs\/cookbook\/06-style-prop-value-px.md b\/docs\/cookbook\/06-style-prop-value-px.md\nindex 5ee2691797..642f33d360 100644\n--- a\/docs\/cookbook\/06-style-prop-value-px.md\n+++ b\/docs\/cookbook\/06-style-prop-value-px.md\n@@ -7,11 +7,7 @@ prev: jsx-root-node-count.html\n next: children-prop-type.html\n ---\n \n-### Problem\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 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@@ -20,8 +16,7 @@ var divStyle = {height: 10}; \/\/ rendered as \"height:10px\"\n React.renderComponent(

Hello World!<\/div>, mountNode);\n ```\n \n-### Discussion\n-See [Inline Styles](\/react\/docs\/cookbook\/inline-styles.html) for more info.\n+See [Inline Styles](\/react\/docs\/cookbook\/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\/07-children-prop-type tip.md b\/docs\/cookbook\/07-children-prop-type tip.md\ndeleted file mode 100644\nindex 0781d9758c..0000000000\n--- a\/docs\/cookbook\/07-children-prop-type tip.md\t\n+++ \/dev\/null\n@@ -1,12 +0,0 @@\n----\n-id: children-prop-type-tip\n-title: Type of the children prop\n-layout: cookbook\n-permalink: children-prop-type-tip.html\n-prev: style-prop-value-px.html\n-next: controlled-input-null-value.html\n----\n-\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, 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\/07-children-prop-type.md b\/docs\/cookbook\/07-children-prop-type.md\nindex 72458d628b..4ce5ec7473 100644\n--- a\/docs\/cookbook\/07-children-prop-type.md\n+++ b\/docs\/cookbook\/07-children-prop-type.md\n@@ -7,10 +7,6 @@ prev: style-prop-value-px.html\n next: controlled-input-null-value.html\n ---\n \n-### Problem\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, it returns the component itself when there's only one.\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, 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\/08-controlled-input-null-value tip.md b\/docs\/cookbook\/08-controlled-input-null-value tip.md\ndeleted file mode 100644\nindex 2a3d55b0df..0000000000\n--- a\/docs\/cookbook\/08-controlled-input-null-value tip.md\t\n+++ \/dev\/null\n@@ -1,24 +0,0 @@\n----\n-id: controlled-input-null-value-tip\n-title: Value of null for controlled input\n-layout: cookbook\n-permalink: controlled-input-null-value-tip.html\n-prev: children-prop-type.html\n-next: componentWillReceiveProps-not-triggered-after-mounting.html\n----\n-\n-Specifying the `value` prop on a [controlled component](\/react\/docs\/cookbook\/forms.html) prevents the user from changing the input unless you desire so.\n-\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 *\/\n-\n-React.renderComponent(, mountNode);\n-\n-setTimeout(function() {\n- React.renderComponent(, mountNode);\n-}, 2000);\n-```\ndiff --git a\/docs\/cookbook\/08-controlled-input-null-value.md b\/docs\/cookbook\/08-controlled-input-null-value.md\nindex fcd1ee6c79..8c2092087e 100644\n--- a\/docs\/cookbook\/08-controlled-input-null-value.md\n+++ b\/docs\/cookbook\/08-controlled-input-null-value.md\n@@ -7,11 +7,11 @@ prev: children-prop-type.html\n next: componentWillReceiveProps-not-triggered-after-mounting.html\n ---\n \n-### Problem\n-You specified a `value` parameter for your form input, but the input value can still be modified, contrary to [what you'd expect](\/react\/docs\/cookbook\/forms.html).\n+Specifying the `value` prop on a [controlled component](\/react\/docs\/cookbook\/forms.html) prevents the user from changing the input unless you desire so.\n \n-### Solution\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+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\/09-componentWillReceiveProps-not-triggered-after-mounting-tip.md b\/docs\/cookbook\/09-componentWillReceiveProps-not-triggered-after-mounting-tip.md\ndeleted file mode 100644\nindex 2eb6ad0baa..0000000000\n--- a\/docs\/cookbook\/09-componentWillReceiveProps-not-triggered-after-mounting-tip.md\n+++ \/dev\/null\n@@ -1,12 +0,0 @@\n----\n-id: componentWillReceiveProps-not-triggered-after-mounting-tip\n-title: componentWillReceiveProps not triggered after mounting\n-layout: cookbook\n-permalink: componentWillReceiveProps-not-triggered-after-mounting-tip.html\n-prev: controlled-input-null-value.html\n-next: props-in-getInitialSate-as-anti-pattern.html\n----\n-\n-`componentWillReceiveProps` isn't triggered after the node is put on scene. This is by design. Check out [other lifecycle methods](\/react\/docs\/cookbook\/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 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\/09-componentWillReceiveProps-not-triggered-after-mounting.md b\/docs\/cookbook\/09-componentWillReceiveProps-not-triggered-after-mounting.md\nindex 4c73adbf8b..45e22e3264 100644\n--- a\/docs\/cookbook\/09-componentWillReceiveProps-not-triggered-after-mounting.md\n+++ b\/docs\/cookbook\/09-componentWillReceiveProps-not-triggered-after-mounting.md\n@@ -7,11 +7,6 @@ prev: controlled-input-null-value.html\n next: props-in-getInitialSate-as-anti-pattern.html\n ---\n \n-### Problem\n-`componentWillReceiveProps` isn't triggered after the node is put on scene.\n+`componentWillReceiveProps` isn't triggered after the node is put on scene. This is by design. Check out [other lifecycle methods](\/react\/docs\/cookbook\/component-specs.html) for the one that suits your needs.\n \n-### Solution\n-This is by design. Check out [other lifecycle methods](\/react\/docs\/cookbook\/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 acting upon changes; not triggering it at mounting (where there are no old props) helps in defining what the method does.\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\/10-props-in-getInitialSate-as-anti-pattern-tip.md b\/docs\/cookbook\/10-props-in-getInitialSate-as-anti-pattern-tip.md\ndeleted file mode 100644\nindex 60c15934bd..0000000000\n--- a\/docs\/cookbook\/10-props-in-getInitialSate-as-anti-pattern-tip.md\n+++ \/dev\/null\n@@ -1,62 +0,0 @@\n----\n-id: props-in-getInitialSate-as-anti-pattern-tip\n-title: props in getInitialState is an anti-pattern\n-layout: cookbook\n-permalink: props-in-getInitialSate-as-anti-pattern-tip.html\n-prev: componentWillReceiveProps-not-triggered-after-mounting.html\n-next: dom-event-listeners.html\n----\n-\n-> Note:\n->\n-> This isn't really a React-specific tip, as such anti-patterns often occur in code in general; in this case, React simply points them out more clearly.\n-\n-Using props, passed down from parent, to generate state in `getInitialState` often leads to duplication of \"source of truth\", i.e. where the real data is. Whenever possible, compute values on-the-fly to ensure that they don't get out of sync later on and cause maintenance trouble.\n-\n-Bad example:\n-\n-```js\n-\/** @jsx React.DOM *\/\n-\n-var MessageBox = React.createClass({\n- getInitialState: function() {\n- return {nameWithQualifier: \"Mr. \" + this.props.name};\n- },\n- render: function() {\n- return

{this.state.nameWithQualifier}<\/div>;\n- }\n-});\n-\n-React.renderComponent(, mountNode);\n-```\n-\n-Better:\n-\n-```js\n-\/** @jsx React.DOM *\/\n-\n-var MessageBox = React.createClass({\n- render: function() {\n- return

{\"Mr. \" + this.props.name}<\/div>;\n- }\n-});\n-\n-React.renderComponent(, mountNode);\n-```\n-\n-For more complex logic:\n-\n-```js\n-\/** @jsx React.DOM *\/\n-\n-var MessageBox = React.createClass({\n- render: function() {\n- return

{this.getNameWithQualifier(this.props.name)}<\/div>;\n- },\n- getNameWithQualifier: function(name) {\n- return 'Mr. ' + name;\n- }\n-});\n-\n-React.renderComponent(, mountNode);\n-```\ndiff --git a\/docs\/cookbook\/10-props-in-getInitialSate-as-anti-pattern.md b\/docs\/cookbook\/10-props-in-getInitialSate-as-anti-pattern.md\nindex 8fd1347ba7..ebe195e859 100644\n--- a\/docs\/cookbook\/10-props-in-getInitialSate-as-anti-pattern.md\n+++ b\/docs\/cookbook\/10-props-in-getInitialSate-as-anti-pattern.md\n@@ -7,8 +7,13 @@ prev: componentWillReceiveProps-not-triggered-after-mounting.html\n next: dom-event-listeners.html\n ---\n \n-### Problem\n-You're using `this.props` in a component `getInitialSate`, like so:\n+> Note:\n+>\n+> This isn't really a React-specific tip, as such anti-patterns often occur in code in general; in this case, React simply points them out more clearly.\n+\n+Using props, passed down from parent, to generate state in `getInitialState` often leads to duplication of \"source of truth\", i.e. where the real data is. Whenever possible, compute values on-the-fly to ensure that they don't get out of sync later on and cause maintenance trouble.\n+\n+Bad example:\n \n ```js\n \/** @jsx React.DOM *\/\n@@ -25,8 +30,7 @@ var MessageBox = React.createClass({\n React.renderComponent(, mountNode);\n ```\n \n-### Solution\n-Avoid this (see below for explanation). Compute it directly inside `render`:\n+Better:\n \n ```js\n \/** @jsx React.DOM *\/\n@@ -56,8 +60,3 @@ var MessageBox = React.createClass({\n \n React.renderComponent(, mountNode);\n ```\n-\n-### Discussion\n-This isn't really a React-specific tip, as such anti-patterns often occur in code in general; in this case, React simply points them out more clearly.\n-\n-Using props, passed down from parent, to generate state often leads to duplication of \"source of truth\", i.e. where the real data is. Whenever possible, compute values on-the-fly to ensure that they don't get out of sync later on and cause maintenance trouble.\ndiff --git a\/docs\/cookbook\/11-dom-event-listeners tip.md b\/docs\/cookbook\/11-dom-event-listeners tip.md\ndeleted file mode 100644\nindex f83798a4b0..0000000000\n--- a\/docs\/cookbook\/11-dom-event-listeners tip.md\t\n+++ \/dev\/null\n@@ -1,40 +0,0 @@\n----\n-id: dom-event-listeners-tip\n-title: DOM event listeners in a component\n-layout: cookbook\n-permalink: dom-event-listeners-tip.html\n-prev: props-in-getInitialSate-as-anti-pattern.html\n-next: initial-ajax.html\n----\n-\n-> Note:\n->\n-> This entry shows how to attach DOM events not provided by React ([check here for more info](\/react\/docs\/cookbook\/events.html)). This is good for integrations with other libraries such as jQuery.\n-\n-Try to resize the window:\n-\n-```js\n-\/** @jsx React.DOM *\/\n-\n-var Box = React.createClass({\n- getInitialState: function() {\n- return {windowWidth: window.innerWidth};\n- },\n- handleResize: function(e) {\n- this.setState({windowWidth: window.innerWidth});\n- },\n- componentDidMount: function() {\n- window.addEventListener(\"resize\", this.handleResize);\n- },\n- componentWillUnmount: function() {\n- window.removeEventListener(\"resize\", this.handleResize);\n- },\n- render: function() {\n- return

Current window width: {this.state.windowWidth}<\/div>;\n- }\n-});\n-\n-React.renderComponent(, mountNode);\n-```\n-\n-`componentDidMount` is called after the component's mounted and has a DOM representation. This is often a place where you'd attach generic DOM events.\ndiff --git a\/docs\/cookbook\/11-dom-event-listeners.md b\/docs\/cookbook\/11-dom-event-listeners.md\nindex 3de316ccb6..1336953ac2 100644\n--- a\/docs\/cookbook\/11-dom-event-listeners.md\n+++ b\/docs\/cookbook\/11-dom-event-listeners.md\n@@ -7,10 +7,6 @@ prev: props-in-getInitialSate-as-anti-pattern.html\n next: initial-ajax.html\n ---\n \n-### Problem\n-You want to listen to an event inside a component.\n-\n-### Solution\n > Note:\n >\n > This entry shows how to attach DOM events not provided by React ([check here for more info](\/react\/docs\/cookbook\/events.html)). This is good for integrations with other libraries such as jQuery.\n@@ -41,5 +37,4 @@ var Box = React.createClass({\n React.renderComponent(, mountNode);\n ```\n \n-### Discussion\n `componentDidMount` is called after the component's mounted and has a DOM representation. This is often a place where you'd attach generic DOM events.\ndiff --git a\/docs\/cookbook\/12-initial-ajax tip.md b\/docs\/cookbook\/12-initial-ajax tip.md\ndeleted file mode 100644\nindex 600d9e8a5a..0000000000\n--- a\/docs\/cookbook\/12-initial-ajax tip.md\t\n+++ \/dev\/null\n@@ -1,45 +0,0 @@\n----\n-id: initial-ajax-tip\n-title: Load initial data via AJAX\n-layout: cookbook\n-permalink: initial-ajax-tip.html\n-prev: dom-event-listeners.html\n----\n-\n-Fetch data in `componentDidMount`. When they arrive, put them inside your state then render them.\n-\n-This example fetches the desired Github user's lastest gist:\n-\n-```js\n-\/** @jsx React.DOM *\/\n-\n-var UserGist = React.createClass({\n- getInitialState: function() {\n- return {\n- username: '',\n- lastGistUrl: ''\n- };\n- },\n- componentDidMount: function() {\n- $.get(this.props.source, function(result) {\n- var lastGist = result[0];\n- this.setState({\n- username: lastGist.user.login,\n- lastGistUrl: lastGist.html_url\n- });\n- }.bind(this));\n- },\n- render: function() {\n- return (\n-

\n- {this.state.username}'s last gist is\n- here<\/a>.\n- <\/div>\n- );\n- }\n-});\n-\n-React.renderComponent(\n- , mountNode\n-);\n-```\ndiff --git a\/docs\/cookbook\/12-initial-ajax.md b\/docs\/cookbook\/12-initial-ajax.md\nindex 1adaca5f0d..af8676700b 100644\n--- a\/docs\/cookbook\/12-initial-ajax.md\n+++ b\/docs\/cookbook\/12-initial-ajax.md\n@@ -4,12 +4,9 @@ title: Load initial data via AJAX\n layout: cookbook\n permalink: initial-ajax.html\n prev: dom-event-listeners.html\n+next: false-in-jsx.html\n ---\n \n-### Problem\n-You want to load initial ajax data.\n-\n-### Solution\n Fetch data in `componentDidMount`. When they arrive, put them inside your state then render them.\n \n This example fetches the desired Github user's lastest gist:\ndiff --git a\/docs\/cookbook\/13-false-in-jsx tip.md b\/docs\/cookbook\/13-false-in-jsx tip.md\ndeleted file mode 100644\nindex a419c0af13..0000000000\n--- a\/docs\/cookbook\/13-false-in-jsx tip.md\t\n+++ \/dev\/null\n@@ -1,29 +0,0 @@\n----\n-id: false-in-jsx-tip\n-title: False in JSX\n-layout: cookbook\n-permalink: initial-ajax.html\n-prev: initial-ajax.html\n----\n-\n-Here's how `false` renders in different contexts:\n-\n-Renders as `id=\"false\"`:\n-```js\n-\/** @jsx React.DOM *\/\n-React.renderComponent(

, mountNode);\n-```\n-\n-String \"false\" as input value:\n-```js\n-\/** @jsx React.DOM *\/\n-React.renderComponent(, mountNode);\n-```\n-\n-No child:\n-```js\n-\/** @jsx React.DOM *\/\n-React.renderComponent(

{false}<\/div>, mountNode);\n-```\n-\n-The reason why this one doesn't render as the string `\"false\"` as a `div` child is to allow the more common use-case: `

{x > 1 && You have more than one item}<\/div>`.\ndiff --git a\/docs\/cookbook\/13-false-in-jsx.md b\/docs\/cookbook\/13-false-in-jsx.md\nindex f325a0cab9..f0fb81e966 100644\n--- a\/docs\/cookbook\/13-false-in-jsx.md\n+++ b\/docs\/cookbook\/13-false-in-jsx.md\n@@ -1,15 +1,13 @@\n ---\n-id: false-in-jsx\n+id: false-in-jsx-tip\n title: False in JSX\n layout: cookbook\n-permalink: initial-ajax.html\n+permalink: false-in-jsx.html\n prev: initial-ajax.html\n ---\n \n-### Problem\n-How does `undefined` and `false` behave as an attribute value and as a child component?\n+Here's how `false` renders in different contexts:\n \n-### Solution\n Renders as `id=\"false\"`:\n ```js\n \/** @jsx React.DOM *\/\n@@ -28,5 +26,4 @@ No child:\n React.renderComponent(

{false}<\/div>, mountNode);\n ```\n \n-### Discussion\n-The reason why the last one doesn't render as the string `\"false\"` as a `div` child is to allow the more common use-case: `

{x > 1 && You have more than one item}<\/div>`.\n+The reason why this one doesn't render as the string `\"false\"` as a `div` child is to allow the more common use-case: `

{x > 1 && You have more than one item}<\/div>`.\n"}

dillon1000/react

Files changed