Update README.md, typo: satus -> status
Merge pull request #337 from Radagaisus/patch-1

Update README.md, typo: satus -> status
Allow rack/mount cascading to be skipped on header

When using header versioning with the :strict policy, Grape currently
returns the appropriate error (406 Not Acceptable) but it also returns a
X-Cascade header indicating to rack it should keep looking for
other routes.

While this behavior is expected for various applications, some may need
to skip the cascading and explicitly return the error to the requester.

For that, a :cascade option was added to the version method. The default
value is true (keeping backwards compat), meaning that 406 errors shall
be raised along with X-Cascade headers, just like before. Though, if set
to false, it 406 errors shall be raised with no X-Cascade headers,
therefore telling the router it should not lookup other routes.
Minor README edits for cascade.
Extend :cascade to work with all versioning strategies

The :cascade option allows preventing X-Cascade to be returned on
response headers. For Rails users, this is useful because your
API exceptions don't get rendered/handled by Rails, but actually sent to
users. This is particularly useful if you want your user to receive an
error exception in the same format your API supports, and not an
unexpected HTML page.

A more in-depth explanation of :cascade was moved into the code and the
overview was inserted on the main README on the exceptions section.

This commit also changes the order in which versioning strategies are
presented. The order is now consistent with the order in which the
strategies were first presented. It also presents the default one,
before introducing non-defaults.
Delete X-Cascade header for default behavior.
The long extension has been annoying me for a while.
Updated CHANGELOG, preparing for a release.
Incremented version to 0.3.1.
Fixed markdown links.
add Content-Type header to the 405 response
fix spec title
add contribution to CHANGELOG
Test for JSONP support
Fix: added custom formatter to spec.
add specs
send text/plain as content-type instead of an empty string
Mime-based content negotiation is easier to read

It's still based on a big regular expression, but hopefully the comments and
wording make it a little less scary for someone scanning through the code.

(still no idea what `String#gsub(/\b/, '')` does, though)
Remove a mysterious zero-width replacement

As far as I can tell, it replaced zero-width breakers with zero-width
replacement (that is, it seemed to have no effect).

No tests failed when I removed it. If it does do something, maybe a test or
a comment would be handy to explain the intention.

It was introduced in commit f7728b88c8cb33e5a783f7a779c761196d697343 -- the
original implementation.
Adds Ruby 2.0.0 to .travis.yml