[Catalyst-commits] r14204 - trunk/examples/CatalystAdvent/root/2011/pen

[lukast at dev.catalyst.perl.org]

Author: lukast
Date: 2011-12-10 21:19:46 +0000 (Sat, 10 Dec 2011)
New Revision: 14204

Modified:
   trunk/examples/CatalystAdvent/root/2011/pen/controllerrole_chainaction_massascre_1.pod
Log:
corrected typo in chainaction article

Modified: trunk/examples/CatalystAdvent/root/2011/pen/controllerrole_chainaction_massascre_1.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2011/pen/controllerrole_chainaction_massascre_1.pod	2011-12-10 20:18:13 UTC (rev 14203)
+++ trunk/examples/CatalystAdvent/root/2011/pen/controllerrole_chainaction_massascre_1.pod	2011-12-10 21:19:46 UTC (rev 14204)
@@ -640,18 +640,18 @@
 
 When you add all these information, everybody (including yourself) will be able to 
 understand the purpose of your roles, and how to use them. Well, not everybody will 
-be able to understand your code. Maybe not even you. But the chance that youself and others
-understand und use your code increases.
+be able to understand your code. Maybe not even you. But the chance that yourself and others
+understand and use your code increases.
 
 =head2 Conclusion
 
 =over
 
-=item * Chaining actions can make your code more reusabel
+=item * Chaining actions can make your code more reusable
 
 =item * Making your actions as atomic as possible increases flexibility and reusability
 
-=item * It is possible to write reuseabe, chained actions in Moose::Role's
+=item * It is possible to write reuseable, chained actions in Moose::Role's
 
 =item * Making your roles as configurable as possible dramatically increases the chance that you (and others) find it usefull in other projects