[Catalyst-commits] r8512 - trunk/examples/CatalystAdvent/root/2006

[jester at dev.catalyst.perl.org]

Author: jester
Date: 2008-10-07 17:49:53 +0100 (Tue, 07 Oct 2008)
New Revision: 8512

Modified:
   trunk/examples/CatalystAdvent/root/2006/17.pod
Log:
Fixed some typos.

Modified: trunk/examples/CatalystAdvent/root/2006/17.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2006/17.pod	2008-10-06 18:54:31 UTC (rev 8511)
+++ trunk/examples/CatalystAdvent/root/2006/17.pod	2008-10-07 16:49:53 UTC (rev 8512)
@@ -5,13 +5,13 @@
 =head2 Introduction
 
 Any non-trivial project needs solid QA, and most Catalyst projects are
-not trivial. This article will guide through some specific way to test
+not trivial. This article will guide you through some specific ways to test
 your controllers.
 
 General Perl testing is beyond the scope of this discussion, but you
 can read about it in L<Test::Tutorial>, L<Test::Simple>,
 L<Test::More>, and the 
-L<Perl Testing Notebook|http://www.oreilly.com/catalog/perltestingadn> 
+L<Perl Testing Notebook|http://www.oreilly.com/catalog/perltestingadn>, 
 which is highly recommended.
 
 =head2 Think outside the box with Test::WWW::Mechanize::Catalyst
@@ -154,7 +154,7 @@
 
 This concludes our example, but remember we're just scratching the
 surface of Test::WWW::Mechanize::Catalyst. You can submit forms,
-authenticate using cookies, please explore this further:
+authenticate using cookies, and do much more. Please explore this further:
 
 L<Test::WWW::Mechanize::Catalyst>, L<Test::WWW::Mechanize>,
 L<WWW::Mechanize>, L<LWP::UserAgent>.
@@ -162,11 +162,11 @@
 =head2 Chuck Norris tests his Catalyst controllers with Test::More
 
 While testing your app from outside is very useful to check if your
-features are implemented as planned, more rigurous testing is needed
+features are implemented as planned, more rigorous testing is needed
 to ensure the B<corectness of your code>.
 
 When testing controllers you basically want to fake their context, run the 
-action and check the stash.
+action, and check the stash.
 
 Let's do just that. Open a new file, t/controller_root_unit.t:
 
@@ -189,7 +189,7 @@
 You have there a fake model that always gives 5 days till xmas, and a
 fake context that returns the fake model.
 
-Later on, after the action is ran, you can pick up the results from
+Later on, after the action is run, you can pick up the results from
 the fake context's stash.
 
 When unit testing controllers, just make sure you provide all the