Set textarea value when changing content

At http://jsfiddle.net/spicyj/W4QLq/, typing into the textbox would cause
clicking the button to do nothing; now it should work.
Don't set value if it'll be a noop
Exposing ReactProps as React.Props

Right now, even though ReactProps is committed, there is no way to use it as it is not exposed.
Adding JSX pitfalls section in the docs
Don't let textarea value change via textContent

Turns out my tests before weren't particularly useful because
receiveProps doesn't end up running componentDidUpdate since the
transaction never finishes. Now they use replaceProps instead (and I
verified that commenting out the "rootNode.value = ..." line makes the
tests fail, which wasn't true before).
Fix textchange event enqueueing

(Was broken by e1535fbd71d8c89c82cd9d9073c1ee97ee6a3b00.)
Merge pull request #92 from spicyj/fix-textchange

Fix textchange event enqueueing
Merge pull request #89 from vjeux/patch-4

Exposing ReactProps as React.Props
getDOMNodeID: Don't return .id on random objects

If you defined a global named `id` (a horrible name, I know) then
getDOMNodeID(window) would return that object. Since only DOM nodes can
have IDs, this should be a noop change otherwise.

Test Plan:
Verified that document.documentElement and document.body both support
getAttributeNode properly in latest Chrome and in IE8.
Merge pull request #91 from yungsters/master

Fix `EventPluginRegistry` Unit Tests
Merge pull request #61 from spicyj/getdomnodeid

getDOMNodeID: Don't return .id on random objects
Adds optional callback to `setState`

This commit adds an optional callback as a second argument to
`setState`, to be called after `setState` runs.

We never guarantee synchronous execution of `setState`, and as per
@phunt, we don't want to make that guarantee because we may eventually
batch calls to `setState`.  @jwalke agrees with him.
Updated docs and check for truthiness

Change api docs to reflect presence of the new argument.  In addition,
callback was change to require only a "truthy" value.
markdown syntax

Small problem with markdown syntax in syntax-highlighted block.
Update tutorial.md

The ajax call happens every 5 seconds, not every 60 seconds.
Minor typo.
Minor grammar.
Link to my own blog
Add callbacks to all public-facing state/props methods

All public facing {set,replace,force}{props,state} methods now support
callbacks.
Merge pull request #97 from spicyj/patch-1

Link to my own blog instead of Quora