Merge pull request #964 from bobeagan/patch-2

fix incorrect link
Move grunt/config/jsx/jsx.js to grunt/config/jsx.js.

There used to be more files in that subdirectory.
jsx whitespace codemod utility
Remove build/modules/ at beginning of `grunt` and `grunt test`.

Little-known fact: instead of writing copies of compiled module files to
build/modules/, the bin/jsx-internal script actually just makes hard links
to the master versions of files in the .module-cache/, so re-populating
build/modules/ is very inexpensive.

Closes #856.
Merge pull request #980 from benjamn/issue-856-delete-build-modules

Remove build/modules/ at beginning of `grunt` and `grunt test`.
Upgrade Commoner to v0.9.0 to get rid of output directory locking.

Closes #957.
Merge pull request #981 from benjamn/upgrade-commoner-to-remove-output-directory-locking

Upgrade Commoner to v0.9.0 to get rid of output directory locking.
remove references to react-page
Add warning about object property order.

It's easy to misuse the properties-as-keys feature and end up with children rendered out of order. Add a note and example of how to avoid this.
Fix docs typo
Merge pull request #880 from jbaiter/reactlink_checkbox

Support two-way binding for checkboxes in LinkedValueMixin via 'checkedLink' property
Update 09.2-form-input-binding-sugar.md
Fix animation example code

key should never be index into an array or there are bugs. Especially in
transitions.

Fixes #853
Use querySelectorAll instead of getElementsByName in ReactDOMInput.

We've been able to use `querySelectorAll` in all the browsers that we
support for some time now, but we haven't been able to test code that uses
it in the older version of `jsdom` that we were using, until recently.

Besides the general goal of modernizing our code, the impetus for this
specific change is that I'm trying to support testing without having to
render nodes into an actual document. The `.getElementsByName` method is
only defined on `document` and only works if the nodes you care about are
contained by the document.

On the other hand, `querySelectorAll` works on any DOM node, and allows a
more precise selection of just the `<input type="radio">` elements that
have the appropriate name.

IE8's implementation of `querySelectorAll` supports attribute-based
selectors, which is all we need here.
Warn for numeric object properties

Numeric keys will be ordered sequentially in Chrome/Firefox.

Warn the user if such keys are set on a child.
fix grammar mistake
Merge pull request #995 from Contra/patch-1

fix grammar mistake (reconciliation docs)
Merge pull request #985 from petehunt/remove-react-page

Remove references to react-page
Support `children` and `ref` for `cloneWithProps()`

We're not handling these correctly.
Fix warning for numeric properties

Number('.1') === 0.1, and react uses dot-prefixed keys
for children. Whoops. Nuke the non-numeric requirement, and just
check a regex. This seems performant enough in micro-benchmarks:
http://jsperf.com/numericlike