{"body":"","patch":"diff --git a\/docs\/docs\/02-displaying-data.md b\/docs\/docs\/02-displaying-data.md\nindex 1305293cf8..719bb7500c 100644\n--- a\/docs\/docs\/02-displaying-data.md\n+++ b\/docs\/docs\/02-displaying-data.md\n@@ -8,7 +8,6 @@ next: jsx-in-depth.html\n \n The most basic thing you can do with a UI is display some data. React makes it easy to display data and automatically keeps the interface up-to-date when the data changes.\n \n-\n ## Getting Started\n \n Let's look at a really simple example. Create a `hello-react.html` file with the following code:\n@@ -56,7 +55,6 @@ setInterval(function() {\n }, 500);\n ```\n \n-\n ## Reactive Updates\n \n Open `hello-react.html` in a web browser and type your name into the text field. Notice that React is only changing the time string in the UI — any input you put in the text field remains, even though you haven't written any code to manage this behavior. React figures it out for you and does the right thing.\n@@ -65,7 +63,6 @@ The way we are able to figure this out is that React does not manipulate the DOM\n \n The inputs to this component are called `props` — short for \"properties\". They're passed as attributes in JSX syntax. You should think of these as immutable within the component, that is, **never write to `this.props`**.\n \n-\n ## Components are Just Like Functions\n \n React components are very simple. You can think of them as simple functions that take in `props` and `state` (discussed later) and render HTML. With this in mind, components are easy to reason about.\n@@ -74,7 +71,6 @@ React components are very simple. You can think of them as simple functions that\n >\n > **One limitation**: React components can only render a single root node. If you want to return multiple nodes they *must* be wrapped in a single root.\n \n-\n ## JSX Syntax\n \n We strongly believe that components are the right way to separate concerns rather than \"templates\" and \"display logic.\" We think that markup and the code that generates it are intimately tied together. Additionally, display logic is often very complex and using template languages to express it becomes cumbersome.\n@@ -99,7 +95,6 @@ JSX is similar to HTML, but not exactly the same. See [JSX gotchas](\/react\/docs\/\n \n [Babel exposes a number of ways to get started using JSX](http:\/\/babeljs.io\/docs\/setup\/), ranging from command line tools to Ruby on Rails integrations. Choose the tool that works best for you.\n \n-\n ## React without JSX\n \n JSX is completely optional; you don't have to use JSX with React. You can create React elements in plain JavaScript using `React.createElement`, which takes a tag name or component, a properties object, and variable number of optional child arguments.\ndiff --git a\/docs\/docs\/02.2-jsx-spread.md b\/docs\/docs\/02.2-jsx-spread.md\nindex 4b6f465941..4cafa8cc28 100644\n--- a\/docs\/docs\/02.2-jsx-spread.md\n+++ b\/docs\/docs\/02.2-jsx-spread.md\n@@ -12,7 +12,7 @@ If you know all the properties that you want to place on a component ahead of ti\n var component = ;\n ```\n \n-## Mutating Props is Bad, mkay\n+## Mutating Props is Bad\n \n If you don't know which properties you want to set, you might be tempted to add them onto the object later:\n \ndiff --git a\/docs\/docs\/02.3-jsx-gotchas.md b\/docs\/docs\/02.3-jsx-gotchas.md\nindex 88a16d74c0..6ab5d4ad56 100644\n--- a\/docs\/docs\/02.3-jsx-gotchas.md\n+++ b\/docs\/docs\/02.3-jsx-gotchas.md\n@@ -27,7 +27,7 @@ If you want to display an HTML entity within dynamic content, you will run into\n

{'First · Second'}<\/div>\n ```\n \n-There are various ways to work-around this issue. The easiest one is to write unicode characters directly in JavaScript. You need to make sure that the file is saved as UTF-8 and that the proper UTF-8 directives are set so the browser will display it correctly.\n+There are various ways to work-around this issue. The easiest one is to write Unicode characters directly in JavaScript. You need to make sure that the file is saved as UTF-8 and that the proper UTF-8 directives are set so the browser will display it correctly.\n \n ```javascript\n

{'First · Second'}<\/div>\ndiff --git a\/docs\/docs\/03-interactivity-and-dynamic-uis.md b\/docs\/docs\/03-interactivity-and-dynamic-uis.md\nindex f26307e477..f5f82c9324 100644\n--- a\/docs\/docs\/03-interactivity-and-dynamic-uis.md\n+++ b\/docs\/docs\/03-interactivity-and-dynamic-uis.md\n@@ -8,7 +8,6 @@ next: multiple-components.html\n \n You've already [learned how to display data](\/react\/docs\/displaying-data.html) with React. Now let's look at how to make our UIs interactive.\n \n-\n ## A Simple Example\n \n ```javascript\n@@ -35,12 +34,10 @@ ReactDOM.render(\n );\n ```\n \n-\n ## Event Handling and Synthetic Events\n \n With React you simply pass your event handler as a camelCased prop similar to how you'd do it in normal HTML. React ensures that all events behave identically in IE8 and above by implementing a synthetic event system. That is, React knows how to bubble and capture events according to the spec, and the events passed to your event handler are guaranteed to be consistent with [the W3C spec](http:\/\/www.w3.org\/TR\/DOM-Level-3-Events\/), regardless of which browser you're using.\n \n-\n ## Under the Hood: Autobinding and Event Delegation\n \n Under the hood, React does a few things to keep your code performant and easy to understand.\n@@ -49,19 +46,16 @@ Under the hood, React does a few things to keep your code performant and easy to\n \n **Event delegation:** React doesn't actually attach event handlers to the nodes themselves. When React starts up, it starts listening for all events at the top level using a single event listener. When a component is mounted or unmounted, the event handlers are simply added or removed from an internal mapping. When an event occurs, React knows how to dispatch it using this mapping. When there are no event handlers left in the mapping, React's event handlers are simple no-ops. To learn more about why this is fast, see [David Walsh's excellent blog post](http:\/\/davidwalsh.name\/event-delegate).\n \n-\n ## Components are Just State Machines\n \n React thinks of UIs as simple state machines. By thinking of a UI as being in various states and rendering those states, it's easy to keep your UI consistent.\n \n In React, you simply update a component's state, and then render a new UI based on this new state. React takes care of updating the DOM for you in the most efficient way.\n \n-\n ## How State Works\n \n A common way to inform React of a data change is by calling `setState(data, callback)`. This method merges `data` into `this.state` and re-renders the component. When the component finishes re-rendering, the optional `callback` is called. Most of the time you'll never need to provide a `callback` since React will take care of keeping your UI up-to-date for you.\n \n-\n ## What Components Should Have State?\n \n Most of your components should simply take some data from `props` and render it. However, sometimes you need to respond to user input, a server request or the passage of time. For this you use state.\n@@ -70,12 +64,11 @@ Most of your components should simply take some data from `props` and render it.\n \n A common pattern is to create several stateless components that just render data, and have a stateful component above them in the hierarchy that passes its state to its children via `props`. The stateful component encapsulates all of the interaction logic, while the stateless components take care of rendering data in a declarative way.\n \n-\n ## What *Should* Go in State?\n \n **State should contain data that a component's event handlers may change to trigger a UI update.** In real apps this data tends to be very small and JSON-serializable. When building a stateful component, think about the minimal possible representation of its state, and only store those properties in `this.state`. Inside of `render()` simply compute any other information you need based on this state. You'll find that thinking about and writing applications in this way tends to lead to the most correct application, since adding redundant or computed values to state means that you need to explicitly keep them in sync rather than rely on React computing them for you.\n \n-## What *Shouldn’t* Go in State?\n+## What *Shouldn't* Go in State?\n \n `this.state` should only contain the minimal amount of data needed to represent your UI's state. As such, it should not contain:\n \ndiff --git a\/docs\/docs\/04-multiple-components.md b\/docs\/docs\/04-multiple-components.md\nindex 03cd8077f5..f6fa1de1e6 100644\n--- a\/docs\/docs\/04-multiple-components.md\n+++ b\/docs\/docs\/04-multiple-components.md\n@@ -8,12 +8,10 @@ next: reusable-components.html\n \n So far, we've looked at how to write a single component to display data and handle user input. Next let's examine one of React's finest features: composability.\n \n-\n ## Motivation: Separation of Concerns\n \n By building modular components that reuse other components with well-defined interfaces, you get much of the same benefits that you get by using functions or classes. Specifically you can *separate the different concerns* of your app however you please simply by building new components. By building a custom component library for your application, you are expressing your UI in a way that best fits your domain.\n \n-\n ## Composition Example\n \n Let's create a simple Avatar component which shows a profile picture and username using the Facebook Graph API.\n@@ -54,14 +52,12 @@ ReactDOM.render(\n );\n ```\n \n-\n ## Ownership\n \n In the above example, instances of `Avatar` *own* instances of `ProfilePic` and `ProfileLink`. In React, **an owner is the component that sets the `props` of other components**. More formally, if a component `X` is created in component `Y`'s `render()` method, it is said that `X` is *owned by* `Y`. As discussed earlier, a component cannot mutate its `props` — they are always consistent with what its owner sets them to. This fundamental invariant leads to UIs that are guaranteed to be consistent.\n \n It's important to draw a distinction between the owner-ownee relationship and the parent-child relationship. The owner-ownee relationship is specific to React, while the parent-child relationship is simply the one you know and love from the DOM. In the example above, `Avatar` owns the `div`, `ProfilePic` and `ProfileLink` instances, and `div` is the **parent** (but not owner) of the `ProfilePic` and `ProfileLink` instances.\n \n-\n ## Children\n \n When you create a React component instance, you can include additional React components or JavaScript expressions between the opening and closing tags like this:\n@@ -72,7 +68,6 @@ When you create a React component instance, you can include additional React com\n \n `Parent` can read its children by accessing the special `this.props.children` prop. **`this.props.children` is an opaque data structure:** use the [React.Children utilities](\/react\/docs\/top-level-api.html#react.children) to manipulate them.\n \n-\n ### Child Reconciliation\n \n **Reconciliation is the process by which React updates the DOM with each new render pass.** In general, children are reconciled according to the order in which they are rendered. For example, suppose two render passes generate the following respective markup:\n@@ -91,7 +86,6 @@ When you create a React component instance, you can include additional React com\n \n Intuitively, `

Paragraph 1<\/p>` was removed. Instead, React will reconcile the DOM by changing the text content of the first child and destroying the last child. React reconciles according to the *order* of the children.\n \n-\n ### Stateful Children\n \n For most components, this is not a big deal. However, for stateful components that maintain data in `this.state` across render passes, this can be very problematic.\n@@ -111,7 +105,6 @@ In most cases, this can be sidestepped by hiding elements instead of destroying\n <\/Card>\n ```\n \n-\n ### Dynamic Children\n \n The situation gets more complicated when the children are shuffled around (as in search results) or if new components are added onto the front of the list (as in streams). In these cases where the identity and state of each child must be maintained across render passes, you can uniquely identify each child by assigning it a `key`:\n@@ -178,7 +171,6 @@ You can also key children by passing a ReactFragment object. See [Keyed Fragment\n \n In React, data flows from owner to owned component through `props` as discussed above. This is effectively one-way data binding: owners bind their owned component's props to some value the owner has computed based on its `props` or `state`. Since this process happens recursively, data changes are automatically reflected everywhere they are used.\n \n-\n ## A Note on Performance\n \n You may be thinking that it's expensive to change data if there are a large number of nodes under an owner. The good news is that JavaScript is fast and `render()` methods tend to be quite simple, so in most applications this is extremely fast. Additionally, the bottleneck is almost always the DOM mutation and not JS execution. React will optimize this for you by using batching and change detection.\ndiff --git a\/docs\/docs\/05-reusable-components.md b\/docs\/docs\/05-reusable-components.md\nindex 55acbbc7d1..75e23858d3 100644\n--- a\/docs\/docs\/05-reusable-components.md\n+++ b\/docs\/docs\/05-reusable-components.md\n@@ -8,7 +8,6 @@ next: transferring-props.html\n \n When designing interfaces, break down the common design elements (buttons, form fields, layout components, etc.) into reusable components with well-defined interfaces. That way, the next time you need to build some UI, you can write much less code. This means faster development time, fewer bugs, and fewer bytes down the wire.\n \n-\n ## Prop Validation\n \n As your app grows it's helpful to ensure that your components are used correctly. We do this by allowing you to specify `propTypes`. `React.PropTypes` exports a range of validators that can be used to make sure the data you receive is valid. When an invalid value is provided for a prop, a warning will be shown in the JavaScript console. Note that for performance reasons `propTypes` is only checked in development mode. Here is an example documenting the different validators provided:\n@@ -79,7 +78,6 @@ React.createClass({\n });\n ```\n \n-\n ## Default Prop Values\n \n React lets you define default values for your `props` in a very declarative way:\n@@ -97,7 +95,6 @@ var ComponentWithDefaultProps = React.createClass({\n \n The result of `getDefaultProps()` will be cached and used to ensure that `this.props.value` will have a value if it was not specified by the parent component. This allows you to safely just use your props without having to write repetitive and fragile code to handle that yourself.\n \n-\n ## Transferring Props: A Shortcut\n \n A common type of React component is one that extends a basic HTML element in a simple way. Often you'll want to copy any HTML attributes passed to your component to the underlying HTML element. To save typing, you can use the JSX _spread_ syntax to achieve this:\n@@ -233,8 +230,6 @@ Methods follow the same semantics as regular ES6 classes, meaning that they don'\n \n Unfortunately ES6 launched without any mixin support. Therefore, there is no support for mixins when you use React with ES6 classes. Instead, we're working on making it easier to support such use cases without resorting to mixins.\n \n-\n-\n ## Stateless Functions\n \n You may also define your React classes as a plain JavaScript function. For example using the stateless function syntax:\n@@ -253,7 +248,6 @@ var HelloMessage = (props) =>

Hello {props.name}<\/div>;\n ReactDOM.render(, mountNode);\n ```\n \n-\n This simplified component API is intended for components that are pure functions of their props. These components must not retain internal state, do not have backing instances, and do not have the component lifecycle methods. They are pure functional transforms of their input, with zero boilerplate.\n \n > NOTE:\n@@ -261,4 +255,3 @@ This simplified component API is intended for components that are pure functions\n > Because stateless functions don't have a backing instance, you can't attach a ref to a stateless function component. Normally this isn't an issue, since stateless functions do not provide an imperative API. Without an imperative API, there isn't much you could do with an instance anyway. However, if a user wants to find the DOM node of a stateless function component, they must wrap the component in a stateful component (eg. ES6 class component) and attach the ref to the stateful wrapper component.\n \n In an ideal world, most of your components would be stateless functions because these stateless components can follow a faster code path within the React core. This is the recommended pattern, when possible.\n-\ndiff --git a\/docs\/docs\/07-forms.md b\/docs\/docs\/07-forms.md\nindex ba8e07eedd..af75d4b23d 100644\n--- a\/docs\/docs\/07-forms.md\n+++ b\/docs\/docs\/07-forms.md\n@@ -32,7 +32,6 @@ Like all DOM events, the `onChange` prop is supported on all native components a\n >\n > For `` and `

`, `onChange` supersedes — and should generally be used instead of — the DOM's built-in [`oninput`](https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/API\/GlobalEventHandlers\/oninput) event handler.\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@@ -70,8 +69,7 @@ This would accept user input but truncate the value to the first 140 characters.\n \n ### Potential Issues With Checkboxes and Radio Buttons\n \n-Be aware that, in an attempt to normalise change handling for checkbox and radio inputs, React uses a `click` event in place of a `change` event. For the most part this behaves as expected, except when calling `preventDefault` in a `change` handler. `preventDefault` stops the browser from visually updating the input, even if `checked` gets toggled. This can be worked around either by removing the call to `preventDefault`, or putting the toggle of `checked` in a `setTimeout`.\n-\n+Be aware that, in an attempt to normalize change handling for checkbox and radio inputs, React uses a `click` event in place of a `change` event. For the most part this behaves as expected, except when calling `preventDefault` in a `change` handler. `preventDefault` stops the browser from visually updating the input, even if `checked` gets toggled. This can be worked around either by removing the call to `preventDefault`, or putting the toggle of `checked` in a `setTimeout`.\n \n ## Uncontrolled Components\n \n@@ -103,10 +101,8 @@ Likewise, `<input>` supports `defaultChecked` and `<select>` supports `defaultVa\n >\n > The `defaultValue` and `defaultChecked` props are only used during initial render. If you need to update the value in a subsequent render, you will need to use a [controlled component](#controlled-components).\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@@ -127,7 +123,6 @@ 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@@ -145,7 +140,6 @@ For HTML, this easily allows developers to supply multiline values. However, sin\n \n If you *do* decide to use children, they will behave like `defaultValue`.\n \n-\n ### Why Select Value?\n \n The selected `<option>` in an HTML `<select>` is normally specified through that option's `selected` attribute. In React, in order to make components easier to manipulate, the following format is adopted instead:\ndiff --git a\/docs\/docs\/08-working-with-the-browser.md b\/docs\/docs\/08-working-with-the-browser.md\nindex 4e2c7ff909..1a7548fda6 100644\n--- a\/docs\/docs\/08-working-with-the-browser.md\n+++ b\/docs\/docs\/08-working-with-the-browser.md\n@@ -8,21 +8,18 @@ next: more-about-refs.html\n \n React provides powerful abstractions that free you from touching the DOM directly in most cases, but sometimes you simply need to access the underlying API, perhaps to work with a third-party library or existing code.\n \n-\n ## The Virtual DOM\n \n-React is so fast because it never talks to the DOM directly. React maintains a fast in-memory representation of the DOM. `render()` methods return a *description* of the DOM, and React can diff this description with the in-memory representation to compute the fastest way to update the browser.\n+React is very fast because it never talks to the DOM directly. React maintains a fast in-memory representation of the DOM. `render()` methods actually return a *description* of the DOM, and React can compare this description with the in-memory representation to compute the fastest way to update the browser.\n \n Additionally, React implements a full synthetic event system such that all event objects are guaranteed to conform to the W3C spec despite browser quirks, and everything bubbles consistently and efficiently across browsers. You can even use some HTML5 events in IE8!\n \n Most of the time you should stay within React's \"faked browser\" world since it's more performant and easier to reason about. However, sometimes you simply need to access the underlying API, perhaps to work with a third-party library like a jQuery plugin. React provides escape hatches for you to use the underlying DOM API directly.\n \n-\n ## Refs and findDOMNode()\n \n To interact with the browser, you'll need a reference to a DOM node. You can attach a `ref` to any element, which allows you to reference the **backing instance** of the component.  This is useful if you need to invoke imperative functions on the component, or want to access the underlying DOM nodes.  To learn more about refs, including ways to use them effectively, see our [refs to components](\/react\/docs\/more-about-refs.html) documentation.\n \n-\n ## Component Lifecycle\n \n Components have three main parts of their lifecycle:\n@@ -33,14 +30,12 @@ Components have three main parts of their lifecycle:\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()` 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@@ -48,26 +43,22 @@ React provides lifecycle methods that you can specify to hook into this process.\n * `componentWillUpdate(object nextProps, object nextState)` is invoked immediately before updating occurs. You cannot call `this.setState()` here.\n * `componentDidUpdate(object prevProps, object prevState)` 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 \n-\n ### Mounted Methods\n \n _Mounted_ composite components also support the following method:\n \n * `component.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-\n ## Browser Support and Polyfills\n \n At Facebook, we support older browsers, including IE8. We've had polyfills in place for a long time to allow us to write forward-thinking JS. This means we don't have a bunch of hacks scattered throughout our codebase and we can still expect our code to \"just work\". For example, instead of seeing `+new Date()`, we can just write `Date.now()`. Since the open source React is the same as what we use internally, we've carried over this philosophy of using forward thinking JS.\n \n In addition to that philosophy, we've also taken the stance that we, as authors of a JS library, should not be shipping polyfills as a part of our library. If every library did this, there's a good chance you'd be sending down the same polyfill multiple times, which could be a sizable chunk of dead code. If your product needs to support older browsers, chances are you're already using something like [es5-shim](https:\/\/github.com\/es-shims\/es5-shim).\n \n-\n ### Polyfills Needed to Support Older Browsers\n \n `es5-shim.js` from [kriskowal's es5-shim](https:\/\/github.com\/es-shims\/es5-shim) provides the following that React needs:\n@@ -94,12 +85,10 @@ The unminified build of React needs the following from [paulmillr's console-poly\n \n When using HTML5 elements in IE8 including `<section>`, `<article>`, `<nav>`, `<header>`, and `<footer>`, it's also necessary to include [html5shiv](https:\/\/github.com\/aFarkas\/html5shiv) or a similar script.\n \n-\n ### Cross-browser Issues\n \n Although React is pretty good at abstracting browser differences, some browsers are limited or present quirky behaviors that we couldn't find a workaround for.\n \n-\n #### onScroll event on IE8\n \n On IE8 the `onScroll` event doesn't bubble and IE8 doesn't have an API to define handlers to the capturing phase of an event, meaning there is no way for React to listen to these events.\ndiff --git a\/docs\/docs\/08.1-more-about-refs.md b\/docs\/docs\/08.1-more-about-refs.md\nindex f1ae11f92a..9caf893737 100644\n--- a\/docs\/docs\/08.1-more-about-refs.md\n+++ b\/docs\/docs\/08.1-more-about-refs.md\n@@ -33,7 +33,6 @@ myComponentInstance.doSomething();\n >\n > This should only ever be used at the top level. Inside components, let your `props` and `state` handle communication with child components, or use one of the other methods of getting a ref (string attribute or callbacks).\n \n-\n ## The ref Callback Attribute\n \n React supports a special attribute that you can attach to any component. The `ref` attribute can be a callback function, and this callback will be executed immediately after the component is mounted. The referenced component will be passed in as a parameter, and the callback function may use the component immediately, or save the reference for future use (or both).\n@@ -67,7 +66,6 @@ When attaching a ref to a DOM component like `<div \/>`, you get the DOM node bac\n \n Note that when the referenced component is unmounted and whenever the ref changes, the old ref will be called with `null` as an argument. This prevents memory leaks in the case that the instance is stored, as in the first example. Also note that when writing refs with inline function expressions as in the examples here, React sees a different function object each time so on every update, ref will be called with `null` immediately before it's called with the component instance.\n \n-\n ## The ref String Attribute\n \n React also supports using a string (instead of a callback) as a ref prop on any component, although this approach is mostly legacy at this point.\n@@ -86,7 +84,6 @@ React also supports using a string (instead of a callback) as a ref prop on any\n     var inputRect = input.getBoundingClientRect();\n     ```\n \n-\n ## A Complete Example\n In order to get a reference to a React component, you can either use `this` to get the current React component, or you can use a ref to get a reference to a component you own. They work like this:\n \ndiff --git a\/docs\/docs\/09-tooling-integration.md b\/docs\/docs\/09-tooling-integration.md\nindex 8f20f7dd2c..7a0360d873 100644\n--- a\/docs\/docs\/09-tooling-integration.md\n+++ b\/docs\/docs\/09-tooling-integration.md\n@@ -12,8 +12,7 @@ Every project uses a different system for building and deploying JavaScript. We'\n \n ### CDN-hosted React\n \n-We provide CDN-hosted versions of React [on our download page](\/react\/downloads.html). These prebuilt files use the UMD module format. Dropping them in with a simple `<script>` tag will inject a `React` global into your environment. It should also work out-of-the-box in CommonJS and AMD environments.\n-\n+We provide CDN-hosted versions of React [on our download page](\/react\/downloads.html). These pre-built files use the UMD module format. Dropping them in with a simple `<script>` tag will inject a `React` global into your environment. It should also work out-of-the-box in CommonJS and AMD environments.\n \n ### Using master\n \n@@ -29,7 +28,6 @@ If you like using JSX, Babel provides an [in-browser ES6 and JSX transformer for\n >\n > The in-browser JSX transformer is fairly large and results in extraneous computation client-side that can be avoided. Do not use it in production — see the next section.\n \n-\n ### Productionizing: Precompiled JSX\n \n If you have [npm](https:\/\/www.npmjs.com\/), you can run `npm install -g babel`. Babel has built-in support for React v0.12 and v0.13. Tags are automatically transformed to their equivalent `React.createElement(...)`, `displayName` is automatically inferred and added to all React.createClass calls.\n@@ -68,7 +66,6 @@ var HelloMessage = React.createClass({\n ReactDOM.render(React.createElement(HelloMessage, { name: \"John\" }), mountNode);\n ```\n \n-\n ### Helpful Open-Source Projects\n \n The open-source community has built tools that integrate JSX with several editors and build systems. See [JSX integrations](https:\/\/github.com\/facebook\/react\/wiki\/Complementary-Tools#jsx-integrations) for the full list.\ndiff --git a\/docs\/docs\/10.1-animation.md b\/docs\/docs\/10.1-animation.md\nindex 5cc1defe88..e0f735a150 100644\n--- a\/docs\/docs\/10.1-animation.md\n+++ b\/docs\/docs\/10.1-animation.md\n@@ -6,7 +6,7 @@ prev: addons.html\n next: two-way-binding-helpers.html\n ---\n \n-React provides a `ReactTransitionGroup` addon component as a low-level API for animation, and a `ReactCSSTransitionGroup` for easily implementing basic CSS animations and transitions.\n+React provides a `ReactTransitionGroup` add-on component as a low-level API for animation, and a `ReactCSSTransitionGroup` for easily implementing basic CSS animations and transitions.\n \n ## High-level API: `ReactCSSTransitionGroup`\n \n@@ -52,6 +52,7 @@ var TodoList = React.createClass({\n   }\n });\n ```\n+\n > Note:\n >\n > You must provide [the `key` attribute](\/react\/docs\/multiple-components.html#dynamic-children) for all children of `ReactCSSTransitionGroup`, even when only rendering a single item. This is how React will determine which children have entered, left, or stayed.\ndiff --git a\/docs\/docs\/10.2-form-input-binding-sugar.md b\/docs\/docs\/10.2-form-input-binding-sugar.md\nindex 605adf708f..8bc351389f 100644\n--- a\/docs\/docs\/10.2-form-input-binding-sugar.md\n+++ b\/docs\/docs\/10.2-form-input-binding-sugar.md\n@@ -68,7 +68,6 @@ Note that checkboxes have a special behavior regarding their `value` attribute,\n <input type=\"checkbox\" checkedLink={this.linkState('booleanValue')} \/>\n ```\n \n-\n ## Under the Hood\n \n There are two sides to `ReactLink`: the place where you create the `ReactLink` instance and the place where you use it. To prove how simple `ReactLink` is, let's rewrite each side separately to be more explicit.\ndiff --git a\/docs\/docs\/10.4-test-utils.md b\/docs\/docs\/10.4-test-utils.md\nindex fa61e65ed2..f7205b7e1f 100644\n--- a\/docs\/docs\/10.4-test-utils.md\n+++ b\/docs\/docs\/10.4-test-utils.md\n@@ -31,7 +31,7 @@ var node = this.refs.button;\n ReactTestUtils.Simulate.click(node);\n ```\n \n-**Changing the value of an input field and then pressing ENTER**\n+**Changing the value of an input field and then pressing ENTER.**\n \n ```javascript\n \/\/ <input ref=\"input\" \/>\n@@ -41,7 +41,7 @@ ReactTestUtils.Simulate.change(node);\n ReactTestUtils.Simulate.keyDown(node, {key: \"Enter\", keyCode: 13, which: 13});\n ```\n \n-*note that you will have to provide any event property that you're using in your component (e.g. keyCode, which, etc...) as React is not creating any of these for you*\n+*Note that you will have to provide any event property that you're using in your component (e.g. keyCode, which, etc...) as React is not creating any of these for you.*\n \n `Simulate` has a method for every event that React understands.\n \n@@ -198,7 +198,6 @@ ReactComponent findRenderedComponentWithType(\n \n Same as `scryRenderedComponentsWithType()` but expects there to be one result and returns that one result, or throws exception if there is any other number of matches besides one.\n \n-\n ## Shallow rendering\n \n Shallow rendering is an experimental feature that lets you render a component \"one level deep\" and assert facts about what its render method returns, without worrying about the behavior of child components, which are not instantiated or rendered. This does not require a DOM.\ndiff --git a\/docs\/docs\/10.7-update.md b\/docs\/docs\/10.7-update.md\nindex 8940e8b488..a9dcdf7f60 100644\n--- a\/docs\/docs\/10.7-update.md\n+++ b\/docs\/docs\/10.7-update.md\n@@ -20,7 +20,7 @@ myData.x.y.z = 7;\n myData.a.b.push(9);\n ```\n \n-you have no way of determining which data has changed since the previous copy has been overwritten. Instead, you need to create a new copy of `myData` and change only the parts of it that need to be changed. Then you can compare the old copy of `myData` with the new one in `shouldComponentUpdate()` using triple-equals:\n+You have no way of determining which data has changed since the previous copy has been overwritten. Instead, you need to create a new copy of `myData` and change only the parts of it that need to be changed. Then you can compare the old copy of `myData` with the new one in `shouldComponentUpdate()` using triple-equals:\n \n ```js\n var newData = deepCopy(myData);\n","parents":["5dc2858bc96f02cf60d33579325ffb4c867a7d8b"],"files":[{"path":"docs\/docs\/02-displaying-data.md","status":"M"},{"path":"docs\/docs\/02.2-jsx-spread.md","status":"M"},{"path":"docs\/docs\/02.3-jsx-gotchas.md","status":"M"},{"path":"docs\/docs\/03-interactivity-and-dynamic-uis.md","status":"M"},{"path":"docs\/docs\/04-multiple-components.md","status":"M"},{"path":"docs\/docs\/05-reusable-components.md","status":"M"},{"path":"docs\/docs\/07-forms.md","status":"M"},{"path":"docs\/docs\/08-working-with-the-browser.md","status":"M"},{"path":"docs\/docs\/08.1-more-about-refs.md","status":"M"},{"path":"docs\/docs\/09-tooling-integration.md","status":"M"},{"path":"docs\/docs\/10.1-animation.md","status":"M"},{"path":"docs\/docs\/10.2-form-input-binding-sugar.md","status":"M"},{"path":"docs\/docs\/10.4-test-utils.md","status":"M"},{"path":"docs\/docs\/10.7-update.md","status":"M"}],"commit":{"revision":"45d4296ac5bfdbfcb905a6dd98ed9b13d68ae223","subject":"Documentation cleanup.","authorName":"Baraa Hamodi","authorEmail":"baraa@optimizely.com","authoredAt":"2015-10-12T15:33:32-04:00","shortRevision":"45d4296ac5"}}</article></body></html>

dillon1000/react

Files changed