[Catalyst-commits] r12199 - trunk/examples/CatalystAdvent/root/2009/pen

[zamolxes at dev.catalyst.perl.org]

Author: zamolxes
Date: 2009-12-06 08:31:53 +0000 (Sun, 06 Dec 2009)
New Revision: 12199

Modified:
   trunk/examples/CatalystAdvent/root/2009/pen/running_cgis.pod
Log:
mod_perl


Modified: trunk/examples/CatalystAdvent/root/2009/pen/running_cgis.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2009/pen/running_cgis.pod	2009-12-06 07:35:14 UTC (rev 12198)
+++ trunk/examples/CatalystAdvent/root/2009/pen/running_cgis.pod	2009-12-06 08:31:53 UTC (rev 12199)
@@ -22,7 +22,7 @@
 =back
 
 L<Catalyst::Controller::WrapCGI> can even be useful for porting a simple
-ModPerl application to Catalyst.
+mod_perl application to Catalyst.
 
 =head2 An Example
 
@@ -93,15 +93,16 @@
 
 Non-Perl CGIs will also work, but of course will not be pre-compiled.
 
-=head2 Porting ModPerl Apps
+=head2 Porting mod_perl Apps
 
-The CGI environment is a bit closer to ModPerl than the regular L<Catalyst>
+The CGI environment is a bit closer to mod_perl than the regular L<Catalyst>
 Controller environment, eg. you can print to C<STDOUT>.
 
 First step would be to rewrite your handler sub to take C<$c> instead of C<$r>
 as a parameter and replace the Apache request methods with the equivalent
 L<Catalyst> framework methods.
 
+
 Replacing things like L<Apache::Session> with L<Catalyst::Plugin::Session> is
 also fairly trivial.