X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Manual.git;a=blobdiff_plain;f=lib%2FCatalyst%2FManual%2FInternals.pod;h=6ba6600383b07228fbb55e1156ae87f601726e14;hp=192d5f4b1bfbbb0a2c47b4adf71b30ec5441450e;hb=be3349e1a2966ee8abc15c1b9a168a3c70125ccb;hpb=bbddff000787154dd9130f45634da8ef06529d86

diff --git a/lib/Catalyst/Manual/Internals.pod b/lib/Catalyst/Manual/Internals.pod
index 192d5f4..6ba6600 100644
--- a/lib/Catalyst/Manual/Internals.pod
+++ b/lib/Catalyst/Manual/Internals.pod
@@ -20,13 +20,13 @@ Catalyst initializes itself in two stages:
 =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>), 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
@@ -90,8 +90,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 populate sthe 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.