Flesh out reference documentation, more API info

[sophiebits]

I created a new "Reference" section on the left with more API docs including a list of all supported tags, attributes, and events. This goes some of the way towards #171 but doesn't really explain how all the delegation works so there's still more work to be done.

See it in action at http://benalpert.com/react/docs/core-api.html.

[vjeux]

This is now react-page

https://github.com/facebook/react-page/

[sophiebits]

True. I seem to remember this getting changed somewhere but this is what master says right now.

[vjeux]

Probably here: http://facebook.github.io/react/docs/tooling-integration.html

[petehunt]

I wonder if we should put parens after method names in the headings.

Core API

I don't really like the word "core", would "top-level" be more descriptive?

In renderComponentToString() could you mention search engine optimization?

Component API

On the docs for transferPropsTo() can you mention:

1. It's really useful if you have a component that basically represents an HTML-like component (i.e. more oriented towards pure display). Usually this is indicated by calling it on the return value of render()
2. It's really dangerous since it can introduce implicit dependencies between components and you should try not to use it that often.

nextState could use backticks

Component Specs and Lifecycle

When I hear "spec" in JS land I think Jasmine test. I don't have a better alternative for you though, so not a huge deal.

setTimeout could use backticks

Tags and Attributes

"to match the DOM" => "to match the DOM API specification"

Event System

nativeEvent needs backticks

DOM differences

"We intentionally break with the spec here" has a comma splice

Other than that lgtm