[Catalyst-commits] r9016 - Catalyst-Manual/5.70/trunk/lib/Catalyst/Manual

[jester at dev.catalyst.perl.org]

Author: jester
Date: 2009-01-06 14:40:12 +0000 (Tue, 06 Jan 2009)
New Revision: 9016

Modified:
   Catalyst-Manual/5.70/trunk/lib/Catalyst/Manual/Internals.pod
Log:
minor fixes

Modified: Catalyst-Manual/5.70/trunk/lib/Catalyst/Manual/Internals.pod
===================================================================
--- Catalyst-Manual/5.70/trunk/lib/Catalyst/Manual/Internals.pod	2009-01-05 19:28:39 UTC (rev 9015)
+++ Catalyst-Manual/5.70/trunk/lib/Catalyst/Manual/Internals.pod	2009-01-06 14:40:12 UTC (rev 9016)
@@ -4,7 +4,7 @@
 
 =head1 DESCRIPTION
 
-This document provides an overview of the internals of
+This document provides a brief overview of the internals of
 Catalyst.  As Catalyst is still developing rapidly, details
 may become out of date: please treat this as a guide, and
 look at the source for the last word.
@@ -13,8 +13,7 @@
 
 =head2 Initialization
 
-Catalyst initializes itself in two stages (I may be wrong in some of
-the details here - AF):
+Catalyst initializes itself in two stages:
 
 =over 4
 
@@ -33,7 +32,7 @@
 (implemented in C<Catalyst::Engine>), Catalyst automatically loads all
 components it finds in the C<$class::Controller>, C<$class::C>,
 C<$class::Model>, C<$class::M>, C<$class::View> and C<$class::V>
-namespaces (using C<Module::Pluggable::Fast>).  A table of actions is built up
+namespaces (using C<Module::Pluggable>).  A table of actions is built up
 and added to on subsequent calls to C<action()>.
 
 =back
@@ -72,7 +71,7 @@
         finalize_body
 
 These steps are normally overloaded from engine classes, and may also be
-extended by plugins.  Extending means using multiple inheritance with L<NEXT>.
+extended by plugins. For more on extending Catalyst, see L<Catalyst::Manual::ExtendingCatalyst>.
 
 The specialized engine classes populate the Catalyst request object with
 information from the underlying layer (C<Apache::Request> or C<CGI::Simple>)