Fix broken tutorial link and change wording
Use script to find remaining 404s. Fix them.
Docs: fix header
Add CDNJS to docs. Fixes #244
Move to using `jstransform` and `esprima-fb` npm modules
Merge pull request #280 from jeffmo/jstransform_npm

Move to using `jstransform` and `esprima-fb` npm modules
[react-tools] Add src/ to files

This is so it's possible to use the original @providesModule source
files in a toolchain that understands those.
Server rendering: rendering of entire document using React.

Summary: Allows rendering of React into the "document" as opposed to into a
particular node. To recap some basics:

document: One level above the <html> tag - like the browser.
document.documentElement: <body>

To support full-page server side rendering, we need to be able to render
*everything* including the HTML/BODY tags. This allows that.
adding better test - moving execution env module.
Merge pull request #289 from jordwalke/ServerRenderingFixes3

Server rendering: rendering of entire document using React.
Benchmarking tool for React application performance

ReactAppPerf wraps core methods and logs info from them; there's no real
UI at this point
Explicit and Implicit Keys Need Separate Namespaces

There are certain cases where you can end up with a collision with an implicit
key (array index) if your explicit key prop is a number. They should use
different namespaces. Therefore I wrap explicit keys in curlies and implicit
array indices in brackets.

I added a simple test case, but another case came up on the mailing list. Where
undefined entries in an array actually results in an entry and therefore an
implicit key.
Add rowSpan DOM property
Add missing "use strict" statement to pass lint

Test Plan:
grunt lint; grunt test
Community round-up #7

http://fooo.fr:4000/react/blog/2013/08/26/community-roundup-7.html
Update the tooling page to include pyReact, react-rails and react-page
Fix capitalization of Tooling Integration page
Support props for <meta> elements.

`content`, `httpEquiv`, `charSet` are all needed. We're currently
working around this in `react-page`.

`content` is the risky one here since we previously supporting using
`content` to set the text content. We removed support for that in
e9980412296b6469f39605f48ea527776d7ac718 so the risk is minimal, there
just might be some lingering old code.

Fixes #292

Test Plan: Visit `data:text/html,<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" charset="utf-8"></head>`

```
var m = document.querySelector('meta');
m.httpEquiv; // Content-Type
m.httpEquiv = 'foo';
m.httpEquiv; // foo

m.charset; // undefined
m.charSet; // undefined
m.getAttribute('charset'); // utf-8
m.setAttribute('charset', 'bar');
m.getAttribute('charset'); // bar

m.content; // text/html; charset=utf-8
m.content = 'baz';
m.content; // baz
```
Allow getInitialState() for mixins

Today mixins can't easily be stateful because they can't provide getInitialState(). This allows multiple getInitialState() methods as long as they don't return objects that have conflicting keys. In that case, we throw.
Sync objMap from upstream