{"patch":"diff --git a\/docs\/docs\/02.1-jsx-in-depth.md b\/docs\/docs\/02.1-jsx-in-depth.md\nindex 2c67b0c8ac..7be45709b9 100644\n--- a\/docs\/docs\/02.1-jsx-in-depth.md\n+++ b\/docs\/docs\/02.1-jsx-in-depth.md\n@@ -22,9 +22,9 @@ var link = React.DOM.a({href: 'http:\/\/facebook.github.io\/react'}, 'React');\n \n We recommend using JSX for many reasons:\n \n-- It's easier to visualize the structure of the DOM.\n-- Designers are more comfortable making changes.\n-- It's familiar for those who have used MXML or XAML.\n+* It's easier to visualize the structure of the DOM.\n+* Designers are more comfortable making changes.\n+* It's familiar for those who have used MXML or XAML.\n \n \n ## The Transform\n@@ -69,8 +69,8 @@ how to setup compilation.\n React and JSX are independent technologies, but JSX was primarily built with\n React in mind. The two valid uses of JSX are:\n \n-- To construct instances of React DOM components (`React.DOM.*`).\n-- To construct instances of composite components created with\n+* To construct instances of React DOM components (`React.DOM.*`).\n+* To construct instances of composite components created with\n `React.createClass()`.\n \n ### React DOM Components\n@@ -160,9 +160,9 @@ var content = {\/* this is a comment *\/}

<\/Container>;\n \n Beyond the compilation step, JSX does not require any special tools.\n \n-- Many editors already include reasonable support for JSX (Vim, Emacs js2-mode).\n-- Linting provides accurate line numbers after compiling without sourcemaps.\n-- Elements use standard scoping so linters can find usage of out-of-scope\n+* Many editors already include reasonable support for JSX (Vim, Emacs js2-mode).\n+* Linting provides accurate line numbers after compiling without sourcemaps.\n+* Elements use standard scoping so linters can find usage of out-of-scope\n components.\n \n ## Prior Work\n@@ -171,8 +171,8 @@ JSX is similar to several other JavaScript embedded XML language\n proposals\/projects. Some of the features of JSX that distinguish it from similar\n efforts include:\n \n-- JSX is a simple syntactic transform.\n-- JSX neither provides nor requires a runtime library.\n-- JSX does not alter or add to the semantics of JavaScript.\n+* JSX is a simple syntactic transform.\n+* JSX neither provides nor requires a runtime library.\n+* JSX does not alter or add to the semantics of JavaScript.\n \n JSX is similar to HTML, but not exactly the same. See [JSX gotchas](.\/jsx-gotchas.html) for some key differences.\ndiff --git a\/docs\/docs\/06-forms.md b\/docs\/docs\/06-forms.md\nindex c851a85252..b2f2323e8f 100644\n--- a\/docs\/docs\/06-forms.md\n+++ b\/docs\/docs\/06-forms.md\n@@ -14,17 +14,17 @@ Form components such as ``, `

`, and `<option>` differ from othe\n \n Form components support a few props that are affected via user interactions:\n \n- - `value`, supported by `<input>` and `<textarea>` components.\n- - `checked`, supported by `<input>` components of type `checkbox` or `radio`.\n- - `selected`, supported by `<option>` components.\n+* `value`, supported by `<input>` and `<textarea>` components.\n+* `checked`, supported by `<input>` components of type `checkbox` or `radio`.\n+* `selected`, supported by `<option>` components.\n \n In HTML, the value of `<textarea>` is set via children. In React, you should use `value` instead.\n \n Form components allow listening for changes by setting a callback to the `onChange` prop. The `onChange` prop works across browsers to fire in response to user interactions when:\n \n- - The `value` of `<input>` or `<textarea>` changes.\n- - The `checked` state of `<input>` changes.\n- - The `selected` state of `<option>` changes.\n+* The `value` of `<input>` or `<textarea>` changes.\n+* The `checked` state of `<input>` changes.\n+* The `selected` state of `<option>` changes.\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 \ndiff --git a\/docs\/docs\/07-working-with-the-browser.md b\/docs\/docs\/07-working-with-the-browser.md\nindex aecf146d75..1aedc64b32 100644\n--- a\/docs\/docs\/07-working-with-the-browser.md\n+++ b\/docs\/docs\/07-working-with-the-browser.md\n@@ -69,39 +69,39 @@ To learn more about refs, including ways to use them effectively, see our [more\n \n Components have three main parts of their lifecycle:\n \n-- **Mounting:** A component is being inserted into the DOM.\n-- **Updating:** A component is being re-rendered to determine if the DOM should be updated.\n-- **Unmounting:** A component is being removed from the DOM.\n+* **Mounting:** A component is being inserted into the DOM.\n+* **Updating:** A component is being re-rendered to determine if the DOM should be updated.\n+* **Unmounting:** A component is being removed from the DOM.\n \n React provides lifecycle methods that you can specify to hook into this process. We provide **will** methods, which are called right before something happens, and **did** methods which are called right after something happens.\n \n \n ### Mounting\n \n- - `getInitialState(): object` is invoked before a component is mounted. Stateful components should implement this and return the initial state data.\n- - `componentWillMount()` is invoked immediately before mounting occurs.\n- - `componentDidMount(DOMElement rootNode)` is invoked immediately after mounting occurs. Initialization that requires DOM nodes should go here.\n+* `getInitialState(): object` is invoked before a component is mounted. Stateful components should implement this and return the initial state data.\n+* `componentWillMount()` is invoked immediately before mounting occurs.\n+* `componentDidMount(DOMElement rootNode)` is invoked immediately after mounting occurs. Initialization that requires DOM nodes should go here.\n \n \n ### Updating\n \n- - `componentWillReceiveProps(object nextProps)` is invoked when a mounted component receives new props. This method should be used to compare `this.props` and `nextProps` to perform state transitions using `this.setState()`.\n- - `shouldComponentUpdate(object nextProps, object nextState): boolean` is invoked when a component decides whether any changes warrant an update to the DOM. Implement this as an optimization to compare `this.props` with `nextProps` and `this.state` with `nextState` and return false if React should skip updating.\n- - `componentWillUpdate(object nextProps, object nextState)` is invoked immediately before updating occurs. You cannot call `this.setState()` here.\n- - `componentDidUpdate(object prevProps, object prevState, DOMElement rootNode)` is invoked immediately after updating occurs.\n+* `componentWillReceiveProps(object nextProps)` is invoked when a mounted component receives new props. This method should be used to compare `this.props` and `nextProps` to perform state transitions using `this.setState()`.\n+* `shouldComponentUpdate(object nextProps, object nextState): boolean` is invoked when a component decides whether any changes warrant an update to the DOM. Implement this as an optimization to compare `this.props` with `nextProps` and `this.state` with `nextState` and return false if React should skip updating.\n+* `componentWillUpdate(object nextProps, object nextState)` is invoked immediately before updating occurs. You cannot call `this.setState()` here.\n+* `componentDidUpdate(object prevProps, object prevState, DOMElement rootNode)` is invoked immediately after updating occurs.\n \n \n ### Unmounting\n \n- - `componentWillUnmount()` is invoked immediately before a component is unmounted and destroyed. Cleanup should go here.\n+* `componentWillUnmount()` is invoked immediately before a component is unmounted and destroyed. Cleanup should go here.\n \n \n ### Mounted Methods\n \n _Mounted_ composite components also support the following methods:\n \n- - `getDOMNode(): DOMElement` can be invoked on any mounted component in order to obtain a reference to its rendered DOM node.\n- - `forceUpdate()` can be invoked on any mounted component when you know that some deeper aspect of the component's state has changed without using `this.setState()`.\n+* `getDOMNode(): DOMElement` can be invoked on any mounted component in order to obtain a reference to its rendered DOM node.\n+* `forceUpdate()` can be invoked on any mounted component when you know that some deeper aspect of the component's state has changed without using `this.setState()`.\n \n > Note:\n >\n","commit":{"authorName":"Paul O’Shannessy","authoredAt":"2013-07-16T23:35:54-07:00","shortRevision":"17d36a4cc3","revision":"17d36a4cc3d16389fa1c3aba338c728524f6f456","authorEmail":"paul@oshannessy.com","subject":"Standardized Markdown lists"},"body":"","parents":["c222f57b0029c3a5b2935a08805fbe122465768e"],"files":[{"path":"docs\/docs\/02.1-jsx-in-depth.md","status":"M"},{"path":"docs\/docs\/06-forms.md","status":"M"},{"path":"docs\/docs\/07-working-with-the-browser.md","status":"M"}]}</article></body></html>

dillon1000/react

Files changed