Document `fetch` usage with Browserify — and switch suggested Promise library to one with a CommoJS API more similar to Fetch.
Dots ruin everything
json formatting doesn't look good with a part of a json file
SP: ot » to
Use fewer words for clarity
Two spaces good, four spaces bad
Backtrack on Promise library switch
Merge pull request #29 from matthew-andrews/npm

Document how to use in Browserify…
Remove form encoded object body.

This was based on a misreading of the URLSearchParams portion of
section 5.2 of https://fetch.spec.whatwg.org/#body-mixin.

Use FormData as the request body to POST form fields instead.
Fix form post content type test.
Remove old body property references.

The body must be consumed through the `text`, `json`, `formData`, or
`blob` functions.
Remove object form encoding test.
Merge pull request #30 from github/remove-form-encode

Remove form encoded object body.
Move body to _body to prevent accessing directly.

The `body` property may be used for Streams in the future. This also
avoids the temptation to access `response.body` directly rather than
going through a body consumer like `response.text()` or
`response.json()`.
Merge pull request #32 from github/hide-body

Move body to _body to prevent direct access
Merge remote-tracking branch 'origin/master' into ie-fixes

Conflicts:
	fetch.js