be more specific about how helpers are exposed in templates

mojolicious · Jan 6, 2015 · 766a1a8 · 766a1a8
1 parent 4256b8d
commit 766a1a8
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 5 deletions.
diff --git a/Changes b/Changes
@@ -1,5 +1,5 @@
 
-5.72  2015-01-06
+5.72  2015-01-07
 
 5.71  2015-01-01
   - Updated Net::DNS::Native requirement to 0.15 for some important bug fixes.

diff --git a/lib/Mojolicious/Guides/Rendering.pod b/lib/Mojolicious/Guides/Rendering.pod
@@ -697,10 +697,10 @@ escaping.
   % end
 
 Similar to stash values you can use a prefix like C<myapp.*> to keep helpers
-from getting exposed in templates and to organize them into namespaces as your
-application grows. Every prefix automatically becomes a helper that returns a
-proxy object containing the current controller object and on which you can
-call the nested helpers.
+from getting exposed in templates as functions, and to organize them into
+namespaces as your application grows. Every prefix automatically becomes a
+helper that returns a proxy object containing the current controller object
+and on which you can call the nested helpers.
 
   use Mojolicious::Lite;