{"patch":"diff --git a\/docs\/docs\/06-forms.md b\/docs\/docs\/06-forms.md\nindex 150ccb6a52..c851a85252 100644\n--- a\/docs\/docs\/06-forms.md\n+++ b\/docs\/docs\/06-forms.md\n@@ -6,8 +6,10 @@ permalink: forms.html\n prev: reusable-components.html\n next: working-with-the-browser.html\n ---\n+\n Form components such as ``, `

`, and `<option>` differ from other native components because they can be mutated via user interactions. These components provide interfaces that make it easier to manage forms in response to user interactions.\n \n+\n ## Interactive Props\n \n Form components support a few props that are affected via user interactions:\n@@ -26,6 +28,7 @@ Form components allow listening for changes by setting a callback to the `onChan\n \n Like all DOM events, the `onChange` prop is supported on all native components and can be used to listen to bubbled change events.\n \n+\n ## Controlled Components\n \n An `<input>` with `value` set is a *controlled* component. In a controlled `<input>`, the value of the rendered element will always reflect the `value` prop. For example:\n@@ -42,12 +45,12 @@ This will render an input that always has a value of `Hello!`. Any user input wi\n   getInitialState: function() {\n     return {value: 'Hello!'};\n   },\n+  handleChange: function(event) {\n+    this.setState({value: event.target.value});\n+  },\n   render: function() {\n     var value = this.state.value;\n     return <input type=\"text\" value={value} onChange={this.handleChange} \/>;\n-  },\n-  handleChange: function(event) {\n-    this.setState({value: event.target.value});\n   }\n ```\n \n@@ -61,6 +64,7 @@ In this example, we are simply accepting the newest value provided by the user a\n \n This would accept user input but truncate the value to the first 140 characters.\n \n+\n ## Uncontrolled Components\n \n An `<input>` that does not supply a `value` (or sets it to `null`) is an *uncontrolled* component. In an uncontrolled `<input>`, the value of the rendered element will reflect the user's input. For example:\n@@ -85,8 +89,10 @@ This example will function much like the **Controlled Components** example above\n \n Likewise, `<input>` supports `defaultChecked` and `<option>` supports `defaultSelected`.\n \n+\n ## Advanced Topics\n \n+\n ### Why Controlled Components?\n \n Using form components such as `<input>` in React presents a challenge that is absent when writing traditional form HTML. For example, in HTML:\n@@ -107,6 +113,7 @@ Unlike HTML, React components must represent the state of the view at any point\n \n Since this method describes the view at any point in time, the value of the text input should *always* be `Untitled`.\n \n+\n ### Why Textarea Value?\n \n In HTML, the value of `<textarea>` is usually set using its children:\n","parents":["ca3564898d6a0fbda451e5b73d3515d9c17589c0"],"commit":{"authoredAt":"2013-07-16T23:29:39-07:00","subject":"Cleanup \"Forms\"","authorEmail":"paul@oshannessy.com","authorName":"Paul O’Shannessy","shortRevision":"602623661a","revision":"602623661af939ccf340eb10dbd9edd64fb3efc0"},"files":[{"path":"docs\/docs\/06-forms.md","status":"M"}],"body":""}</article></body></html>

dillon1000/react

Files changed