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

[caelum at dev.catalyst.perl.org]

Author: caelum
Date: 2011-12-16 20:02:21 +0000 (Fri, 16 Dec 2011)
New Revision: 14223

Modified:
   trunk/examples/CatalystAdvent/root/2011/pen/controllerrole_chainaction_massascre_2.pod
Log:
fix typos and misspellings

Modified: trunk/examples/CatalystAdvent/root/2011/pen/controllerrole_chainaction_massascre_2.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2011/pen/controllerrole_chainaction_massascre_2.pod	2011-12-16 18:04:25 UTC (rev 14222)
+++ trunk/examples/CatalystAdvent/root/2011/pen/controllerrole_chainaction_massascre_2.pod	2011-12-16 20:02:21 UTC (rev 14223)
@@ -206,7 +206,7 @@
 Catalyst controllers are suits.
 You can order clothes by creating dot.pm order sheets.
 
-What we are doing above is a little bit like ordering a red suite with knobs, 
+What we are doing above is a little bit like ordering a red suit with knobs, 
 and 
 adding a note to the sheet which says "please use red knobs aswell".
 We have to remind the taylor of doing that, otherwise he would use
@@ -216,7 +216,7 @@
 The default pattern
 lets the customer choose all material (by setting __PACKAGE__->config).
 We should keep this behaviour, but the default colour should be the same
-as the suite itself. 
+as the suit itself. 
 
 Here we go: (yes, GetRS is the knob-role)
 	
@@ -450,7 +450,7 @@
 
 No matter which way you prefere, you should alwas add a comment to your
 roles documentation if you use a BUILD method. This makes it possible
-to find out why things are going wrong if thei are going wrong.
+to find out why things are going wrong if they are going wrong.
 If your documentation does not include such a hint, a developer using
 your role will most likely not be able to figure out the problem
 in case of conflicts.
@@ -517,7 +517,7 @@
 Adding a few "with"-lines does not hurt me. But this is 
 just my personal opinion. There is more than one way to do it! I am NOT interested
 in a flame-war! L<CatalystX::Component::Traits> is great. I have used it in the past, and 
-I will use it i the future. It has 
+I will use it in the future. It has 
 usefull features, like "trait searching" and "trait merging". And, of course:
 There are these little differences...
 
@@ -703,7 +703,7 @@
 =item * Carefully designing a role, and providing reasonable
 defaults can safe a lot of time when using it.
 
-=item * Moose offers two different ways to influence your controllers
+=item * Moose offers two different ways to influence your controller's
 build process.
 
 =item * BUILDARGS allows you to modify parameters before the object is created