failure to parse params should trigger a 400 Bad Request
Improve poor security recommendation in docs

As reported in #9960, the current documentation recommends an insecure practice for
key generation from a password (a single round of SHA-256). The modified documentation
uses ActiveSupport::KeyGenerator to perform proper key stretching.
Escape multibyte line terminators in JSON encoding

Currently, json/encoding respects the JSON spec (as it should) which 
disallows \n and \r inside strings, escaping them as expected.

Unfortunately, ECMA-262 (Javascript) disallows not only \n and \r in 
strings, but "Line Terminators" which includes U+2028 and U+2029. 
See here: http://bclary.com/2004/11/07/#a-7.3

This pull request adds U+2028 and U+2029 to be escaped.

# Why? 

It's very common to see something like this in a Rails template:

<script type="text/javascript"> 
var posts = <%= @posts.to_json %>;
</script>

If U+2028 or U+2029 are part of any attributes output in the to_json
call, you will end up with an exception.
In Chrome: Uncaught SyntaxError: Unexpected token ILLEGAL 

# Why not?

This is JSON encoding, and the JSON spec is specific about how to 
encode strings. U+2028 and U+2029 don't get special treatment.

Just trying to start a discussion... what do you do in your apps
to deal with this? Is there a convention I'm missing?
Changed grammar for better readability
ARel -> Arel
Added description for mtime
Updated link to peepcode Git screencast
Tried to make the response status code table more readable

By making it the last thing in it's section and adding pseudo row headers
Fixed typo [ci skip]
Clarify arguments of head method
Align table of HTTP status codes with set supported by current Rack
Ruby 1.9 hash syntax for action controller guide
more Ruby 1.9 Hash syntax in our guides
asset guide, match application.rb snippets to the generated file [ci skip]

`if defined?(Bundler)` is no longer used in our current application.rb
Change 'validates_presence_of' to 'presence: true' 

Of course validates_presence_of is still working but it is not explained in the guide, I think consequently should use 'presence: true' in this documentation.
took out unnecessary wordage, changed "number" to "amount"
without autosave option updated records not save

Emphasizing that without autosave option only new
records are saved and updated records are not saved
updated rdoc to reflect info about readonly attribute
documentation fixes for Array.wrap and AR::Validations::AssociatedValidator
Document the fact you can add_index on new columns