Unnecessary peace of text was injected at
507da04a by mistake.

Examples should be not square to visually underline a difference between
Array#in_groups and Array#in_groups_of.

these pages capitalize “HTML5”:

http://en.wikipedia.org/wiki/HTML5
http://dev.w3.org/html5/spec/
http://www.html5rocks.com/en/

Add oscardelben to authors

Optimizing all images used in the guides

Add license field to gemspecs, by Matt Griffin

This reverts commit feaa7b35.

Reason: Incorrect change. That's a Rails 4 feature and will not
obviously work in 3.2.3.

[ci skip]

This reverts commit fa6d921e.

Reason: Not a fan of such massive changes. We usually close such changes
if made to Rails master as a pull request. Following the same principle
here and reverting.

[ci skip]

ConnectionPool wait_timeout no longer used for different types of timeouts. #6441

Adding deep versions of stringify_keys and symbolize_keys (plain and bang) for nested hashes

An AR ConnectionSpec `wait_timeout` is pre-patch used for three
different things:

* mysql2 uses it for MySQL's own wait_timeout (how long MySQL
  should allow an idle connection before closing it), and
  defaults to 2592000 seconds.
* ConnectionPool uses it for "number of seconds to block and
  wait for a connection before giving up and raising a timeout error",
  default 5 seconds.
* ConnectionPool uses it for the Reaper, for deciding if a 'dead'
  connection can be reaped. Default 5 seconds.

Previously, if you want to change these from defaults, you need
to change them all together. This is problematic _especially_
for the mysql2/ConnectionPool conflict, you will generally _not_
want them to be the same, as evidenced by their wildly different
defaults. This has caused real problems for people #6441 #2894

But as long as we're changing this, forcing renaming the
ConnectionPool key to be more specific, it made sense
to seperate the two ConnectionPool uses too -- these two
types of ConnectionPool timeouts ought to be able to be
changed independently, you won't neccesarily want them
to be the same, even though the defaults are (currently)
the same.