@@ -227,13 +227,13 @@ To render a partial as part of a view, you use the +render+ method within the vi
<%=render"menu"%>
</ruby>
This will render a file named <tt>_menu.html.erb</tt> at that point within the view is being rendered. Note the leading underscore character: partials are named with a leading underscore to distinguish them from regular views, even though they are referred to without the underscore. This holds true even when you're pulling in a partial from another folder:
This will render a file named +_menu.html.erb+ at that point within the view is being rendered. Note the leading underscore character: partials are named with a leading underscore to distinguish them from regular views, even though they are referred to without the underscore. This holds true even when you're pulling in a partial from another folder:
<ruby>
<%=render"shared/menu"%>
</ruby>
That code will pull in the partial from <tt>app/views/shared/_menu.html.erb</tt>.
That code will pull in the partial from +app/views/shared/_menu.html.erb+.
h5. Using Partials to Simplify Views
...
...
@@ -252,7 +252,7 @@ One way to use partials is to treat them as the equivalent of subroutines: as a
<%=render"shared/footer"%>
</erb>
Here, the <tt>_ad_banner.html.erb</tt> and <tt>_footer.html.erb</tt> partials could contain content that is shared among many pages in your application. You don't need to see the details of these sections when you're concentrating on a particular page.
Here, the +_ad_banner.html.erb+ and +_footer.html.erb+ partials could contain content that is shared among many pages in your application. You don't need to see the details of these sections when you're concentrating on a particular page.
