diff options
| author | mica eked <micaeked@gmail.com> | 2010-05-04 02:46:21 -0700 |
|---|---|---|
| committer | Xavier Noria <fxn@hashref.com> | 2010-05-04 19:31:40 +0200 |
| commit | d5e3c494781abe0b16b4e40f597ff64f8ad6512f (patch) | |
| tree | 1197b44636eeec40f3802ed638fc94a61f4586c8 | |
| parent | d38b4771f1bf6b7c16f47ec395865e074b64606b (diff) | |
| download | rails-d5e3c494781abe0b16b4e40f597ff64f8ad6512f.tar.gz rails-d5e3c494781abe0b16b4e40f597ff64f8ad6512f.tar.bz2 rails-d5e3c494781abe0b16b4e40f597ff64f8ad6512f.zip | |
typo "<image />" -> "<img />", and typo 'follow' -> 'following'
| -rw-r--r-- | railties/guides/source/layouts_and_rendering.textile | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/railties/guides/source/layouts_and_rendering.textile b/railties/guides/source/layouts_and_rendering.textile index f6b6a1a7cc..7be369453e 100644 --- a/railties/guides/source/layouts_and_rendering.textile +++ b/railties/guides/source/layouts_and_rendering.textile @@ -806,7 +806,7 @@ You can even use dynamic paths such as +cache/#{current_site}/main/display+. h5. Linking to Images with +image_tag+ -The +image_tag+ helper builds an HTML +<image />+ tag to the specified file. By default, files are loaded from +public/images+, note, you must specify the extension, previous versions of Rails would allow you to just call the image name and would append +.png+ if no extension was given, Rails 3.0 does not. +The +image_tag+ helper builds an HTML +<img />+ tag to the specified file. By default, files are loaded from +public/images+, note, you must specify the extension, previous versions of Rails would allow you to just call the image name and would append +.png+ if no extension was given, Rails 3.0 does not. <erb> <%= image_tag "header.png" %> @@ -1154,7 +1154,7 @@ h4. Using Nested Layouts You may find that your application requires a layout that differs slightly from your regular application layout to support one particular controller. Rather than repeating the main layout and editing it, you can accomplish this by using nested layouts (sometimes called sub-templates). Here's an example: -Suppose you have the follow +ApplicationController+ layout: +Suppose you have the following +ApplicationController+ layout: * +app/views/layouts/application.html.erb+ |