Diff of /perl/modperl/docs/trunk/src/docs/2.0/user/handlers/server.pod

Parent Directory | Revision Log | Patch

--- perl/modperl/docs/trunk/src/docs/2.0/user/handlers/server.pod	2004/12/03 00:13:01	109598
+++ perl/modperl/docs/trunk/src/docs/2.0/user/handlers/server.pod	2004/12/03 00:16:32	109599
@@ -303,7 +303,7 @@ anything that can be discarded before th
 
 
 
-=head2 PerlPostConfigHandler
+=head2 C<PerlPostConfigHandler>
 
 The I<post_config> phase happens right after Apache has processed the
 configuration files, before any child processes were spawned (which
@@ -331,7 +331,7 @@ example we used the I<post_config()> han
   }
 
 As you can see, its arguments are identical to the
-L<I<open_logs|/C_PerlOpenLogsHandler_>> phase's handler. In this
+I<L<open_logs|/C_PerlOpenLogsHandler_>> phase's handler. In this
 example handler we don't do much, but logging that the configuration
 was completed and returning right away.
 
@@ -356,7 +356,7 @@ includes another useful example.
 
 
 
-=head2 PerlChildInitHandler
+=head2 C<PerlChildInitHandler>
 
 The I<child_init> phase happens immediately after the child process is
 spawned. Each child process (not a thread!) will run the hooks of this
@@ -396,7 +396,7 @@ I<httpd.conf>:
 
 
 
-=head2 PerlChildExitHandler
+=head2 C<PerlChildExitHandler>
 
 Opposite to the I<child_init> phase, the I<child_exit> phase is
 executed before the child process exits. Notice that it happens only