In the sentence "If <tt>@post.author_ids</tt> is , this would ..." the array  is converted in a footnote, fixed this using <notextile>.
I've personally seen too many newbies get this wrong and pluralize the association
Tagged logging for which Rails has support since [3.2](http://guides.rubyonrails.org/3_2_release_notes.html#tagged-logging). It is trivial & useful but unless somebody explicitly searches API docs, he/she may not know about it. Hence, I added it in guides.
…g in a <pre> block.
Changed the title of the 3.5 chapter from "Using the change Method" to "When to Use the change Method" since the chapter tells the migration definitions supported by the change method. This fix the duplicate ID in the document. I've also changed some of the titles to respect the Guides guidelines.
…ide [ci skip]
… [ci skip] erb tag wasn't closed well
…) [ci skip]
In chapter 2.4 there was an underscore at the start of the attr_readonly method name, this underscore was interpreted as the opening of the <em> tag but it wasn't closed. Worst, the underscore in self.class.serialized_attributes (end of paragraph) was interpreted as the closing of the <em> tag and not as the name of a method.
ActionView decoupling and sprockets-rails tests fail
Method invalid_asset_host! was delegated to controller but sprockets compile assets in their own scope without controller. And if we set asset_host with second parameter it should raise error through invalid_asset_host!. But since controller is nil it cannot be reached.
Option to run `bundle install` after generating new appplication was added recently to rails. Since introduction, it contained a subtle bug that caused it to use `Gemfile` from current directory (if it exists) rather than from generated directory. This also accidentaly caused railties tests to work without any problems - after generating test app it just used `Gemfile` from the repository, rather than the one in generated app. After fixing the bug mentioned above, this of course broke. The easiest way to bypass that is to not generate a `Gemfile` for test application - with such setup Bundler will just use first available `Gemfile` in one of the parent directories.
The cause of the previous revert was bug in bundler that made it hard to make railties test work. Fix for bundler was recently pushed to github, so now we can safely get back to the original commit. This reverts commit 0f5cc34.