diff options
| author | Malav Bhavsar <malav.bhavsar@gmail.com> | 2013-10-10 01:56:42 -0700 |
|---|---|---|
| committer | Malav Bhavsar <malav.bhavsar@gmail.com> | 2013-10-11 22:21:07 -0700 |
| commit | ce46f20d13ca1b45dfd499c359ee8bce7abce1ae (patch) | |
| tree | 5be684806242ed3a6abeed0cf43909e14947ac94 /guides/source/action_view_overview.md | |
| parent | 0061c5e1ef0f7be8946602456a538c263fcafed2 (diff) | |
| download | rails-ce46f20d13ca1b45dfd499c359ee8bce7abce1ae.tar.gz rails-ce46f20d13ca1b45dfd499c359ee8bce7abce1ae.tar.bz2 rails-ce46f20d13ca1b45dfd499c359ee8bce7abce1ae.zip | |
Some fixes in docs [ci skip]
Update a link to point to right section in api docs
Fix a typo
Diffstat (limited to 'guides/source/action_view_overview.md')
| -rw-r--r-- | guides/source/action_view_overview.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/action_view_overview.md b/guides/source/action_view_overview.md index 94aa0f8502..d19dd11181 100644 --- a/guides/source/action_view_overview.md +++ b/guides/source/action_view_overview.md @@ -269,7 +269,7 @@ Rails will render the `_product_ruler` partial (with no data passed to it) betwe ### Layouts -Layouts can be used to render a common view template around the results of Rails controller actions. Typically, every Rails has a couple of overall layouts that most pages are rendered within. For example, a site might have a layout for a logged in user, and a layout for the marketing or sales side of the site. The logged in user layout might include top-level navigation that should be present across many controller actions. The sales layout for a SaaS app might include top-level navigation for things like "Pricing" and "Contact Us." You would expect each layout to have a different look and feel. You can read more details about Layouts in the [Layouts and Rendering in Rails](layouts_and_rendering.html) guide. +Layouts can be used to render a common view template around the results of Rails controller actions. Typically, every Rails application has a couple of overall layouts that most pages are rendered within. For example, a site might have a layout for a logged in user, and a layout for the marketing or sales side of the site. The logged in user layout might include top-level navigation that should be present across many controller actions. The sales layout for a SaaS app might include top-level navigation for things like "Pricing" and "Contact Us." You would expect each layout to have a different look and feel. You can read more details about Layouts in the [Layouts and Rendering in Rails](layouts_and_rendering.html) guide. Partial Layouts --------------- |