X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FInternals.pod;h=bd6692144f202799b1594e536c7a39fac3ae34b9;hb=28198afc276986717a964360d19509950657d0ff;hp=9263addd081278b83b0dd009dea714657fb23c3c;hpb=c312468f8369b9f161352d93750d0aae49ef6093;p=catagits%2FCatalyst-Manual.git

diff --git a/lib/Catalyst/Manual/Internals.pod b/lib/Catalyst/Manual/Internals.pod
index 9263add..bd66921 100644
--- a/lib/Catalyst/Manual/Internals.pod
+++ b/lib/Catalyst/Manual/Internals.pod
@@ -22,11 +22,10 @@ Catalyst initializes itself in two stages:
 When the Catalyst module is imported in the main application
 module, it stores any options.
 
-
 =item 2
 
 When C<< __PACKAGE__->setup >> is called, it evaluates any
-options stored (C<-Debug>, C<-Engine=XXX>), and makes the application
+options stored (C<-Debug>), 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
@@ -39,8 +38,8 @@ C<Catalyst> and from the selected specialized Engine module.
 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>). As each is loaded, if it has a
-L<Catalyst::Component/COMPONENT|COMPONENT> method then this method
+namespaces (using L<Module::Pluggable>). As each is loaded, if it has a
+L<COMPONENT|Catalyst::Component/"COMPONENT"> method then this method
 will be called, and passed that component's configuration. It then returns
 an instance of the component, which becomes the C<$self> when methods in
 that component are called later.
@@ -49,7 +48,7 @@ that component are called later.
 
 Each controller has it's C<register_actions> method called. At this point,
 the subroutine attributes are retrieved from the
-L<MooseX::MethodAttributes::Role::Meta::Map|metaclass>, parsed, and used to
+L<metaclass|MooseX::MethodAttributes::Role::Meta::Map>, parsed, and used to
 build instances of L<Catalyst::Action>, which are then registered with
 the dispatcher.
 
@@ -90,8 +89,8 @@ extend Catalyst.
 These steps are normally overloaded from engine classes, and may also be
 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>)
+The engine class populates the Catalyst request object with
+information from the underlying layer (L<PSGI>)
 during the prepare phase, then push the generated response information down to
 the underlying layer during the finalize phase.