[Catalyst-commits] r11826 - in Catalyst-Manual/5.80/trunk: . lib/Catalyst/Manual

[t0m at dev.catalyst.perl.org]

Author: t0m
Date: 2009-11-14 17:33:28 +0000 (Sat, 14 Nov 2009)
New Revision: 11826

Modified:
   Catalyst-Manual/5.80/trunk/Changes
   Catalyst-Manual/5.80/trunk/lib/Catalyst/Manual/Internals.pod
Log:
Another Pod fix, RT#51488

Modified: Catalyst-Manual/5.80/trunk/Changes
===================================================================
--- Catalyst-Manual/5.80/trunk/Changes	2009-11-14 17:30:26 UTC (rev 11825)
+++ Catalyst-Manual/5.80/trunk/Changes	2009-11-14 17:33:28 UTC (rev 11826)
@@ -1,5 +1,7 @@
 Revision history for Catalyst-Manual
 
+        - Fix POD typos in ::Internals (RT#51488)
+
 5.8001 06 Oct 2009
         - Tutorial
             - Fix RT #46760

Modified: Catalyst-Manual/5.80/trunk/lib/Catalyst/Manual/Internals.pod
===================================================================
--- Catalyst-Manual/5.80/trunk/lib/Catalyst/Manual/Internals.pod	2009-11-14 17:30:26 UTC (rev 11825)
+++ Catalyst-Manual/5.80/trunk/lib/Catalyst/Manual/Internals.pod	2009-11-14 17:33:28 UTC (rev 11826)
@@ -20,13 +20,13 @@
 =item 1
 
 When the Catalyst module is imported in the main application
-module it stores any options.
+module, it stores any options.
 
 
 =item 2
 
-WHen C<< __PACKAGE__->setup >> is called, it evaluates any
-options stored (C<-Debug>, C<-Engine=XXX>), makes the application
+When C<< __PACKAGE__->setup >> is called, it evaluates any
+options stored (C<-Debug>, C<-Engine=XXX>), and makes the application
 inherit from L<Catalyst> (if that hasn't already been done with an
 explicit C<< use base 'Catalyst'; >> or C<< extends 'Catalyst'; >>.
 Any specified plugins are then loaded, the application module is made to