Update the filestore documentation for clear
[ci skip]
Add documentation for #clear on certain Store classes
[ci skip
Add documentation for FileStore#increment and #decrement
[ci skip]
Array#to_formatted_s does not call each element's to_s anymore

Array#to_s calls each element's inspect since ruby 1.9
Remove ambiguity with pluralizations and I18n keys used for association restrict_dependent_destroy errors
Using ruby 1.9 syntax [ci skip]
Rack Sendfile is coming as default now
Added Rack::Sendfile in rake about [ci skip]
Enhancing readability of options for delegate method
Merge branch 'master' of github.com:rails/docrails
Guides fixed typo in index.html.erb file [ci skip]
New output for scaffold generate [ci skip]
fixes the test case of that plugins
Merge pull request #159 from rajcybage/my_fix

fixes the test case of that plugins
document the Rails::ConsoleMethods#helper and #controller methods

Closes rails/rails#11362
use the appropriate RDoc code markup

Thanks @fxn
use strong_params in example
add support for html attributes to grouped_options_for_select
Removed information about creating database[ci skip]

- As default index page is no longer in public folder, rails hits the
  welcome controller in railties for index action
- If the database is not created or username and password are
  incorrect in database.yml, those errors are first shown before index
  action succeeds
- welcome#index succeeds iff the database is created with correct
  details in database.yml
- So this information about creating database is not required in the
  index template
Match Dev/Prod parity for Index Page

With Rails 4 the default index page was moved from a static file `index.html` inside the `public/` folder to an internal controller/view inside of the railties gem. This was to allow use of erb in the default index page and to remove the requirement that new apps must delete a static file to make their index pages work. While this was a good change, the functionality was unexpected to developers who wish to get their apps running in production ASAP. They will create a new app `rails new my app`, start a server to verify it works, then immediately deploy the app to verify that it can start working in production. Unfortunately locally they see a page when they visit `localhost:3000` when they visit their production app they get an error page.

We initially anticipated this problem in the original pull request, but did not properly anticipate the severity or quantity of people who would like this functionality. Having a default index page serves as an excellent litmus test for a passed deploy on default apps, and it is very unexpected to have a page work locally, but not on production. 

This change makes the default index page available in production if the developer has not over-written it by defining their own `root` path inside of routes.