From: Jesse Sheidlower Date: Tue, 6 Jan 2009 14:40:12 +0000 (+0000) Subject: minor fixes X-Git-Tag: v5.8005~226 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=commitdiff_plain;h=9a4214e19f018d581fdec224e13e83ef1b74c3b5 minor fixes --- diff --git a/lib/Catalyst/Manual/Internals.pod b/lib/Catalyst/Manual/Internals.pod index 41efa22..e7aaace 100644 --- a/lib/Catalyst/Manual/Internals.pod +++ b/lib/Catalyst/Manual/Internals.pod @@ -4,7 +4,7 @@ Catalyst::Manual::Internals - Catalyst Internals =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 @@ The coverage is split into initialization and request lifecycle. =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 @@ When the application module makes the first call to C<< __PACKAGE__->action() >> (implemented in C), 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). A table of actions is built up +namespaces (using C). A table of actions is built up and added to on subsequent calls to C. =back @@ -72,7 +71,7 @@ extend Catalyst. finalize_body These steps are normally overloaded from engine classes, and may also be -extended by plugins. Extending means using multiple inheritance with L. +extended by plugins. For more on extending Catalyst, see L. The specialized engine classes populate the Catalyst request object with information from the underlying layer (C or C)