[Catalyst-commits] r7211 - trunk/examples/CatalystAdvent/root/2007

[jrockway at dev.catalyst.perl.org]

Author: jrockway
Date: 2007-12-03 04:26:24 +0000 (Mon, 03 Dec 2007)
New Revision: 7211

Modified:
   trunk/examples/CatalystAdvent/root/2007/3.pod
Log:
tyop fix

Modified: trunk/examples/CatalystAdvent/root/2007/3.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2007/3.pod	2007-12-03 04:10:57 UTC (rev 7210)
+++ trunk/examples/CatalystAdvent/root/2007/3.pod	2007-12-03 04:26:24 UTC (rev 7211)
@@ -88,10 +88,10 @@
 no repeated code.
 
 (BTW, the reason I put user and request into C<< $c->stash >> instead
-of into C<$self> is because we show a message like "Thank you C<$user>
-for approving request C<$request->uuid>".  The begin action that
-inflates and stashes the URL params makes the both the template and
-the controller eaiser to work with.)
+of into C<$self> is because we show a message like "Thank you,
+C<< $user->name >>, for approving request C<< $request->uuid >>".  The
+begin action that inflates and stashes the URL params makes the both
+the template and the controller eaiser to work with.)
 
 =head1 Actions from base controllers
 
@@ -210,7 +210,7 @@
 Whatever work is required to lookup a C<foo> by its C<food> is handled
 completely outside of Catalyst.  This way I can easily write tests,
 and use the code in other applications.  (We save a lot of development
-time by writting common code that can be subclassed for different
+time by writing common code that can be subclassed for different
 clients or interfaces.)
 
 The rest of the action is something like preparing C<$foo> for display