stas        02/02/28 08:59:03

  Modified:    src/docs/1.0/guide control.pod
               src/docs/2.0/user/design design.pod
  Log:
  - more links fixes
  
  Revision  Changes    Path
  1.5       +1 -1      modperl-docs/src/docs/1.0/guide/control.pod
  
  Index: control.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/control.pod,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- control.pod       28 Feb 2002 16:23:22 -0000      1.4
  +++ control.pod       28 Feb 2002 16:59:03 -0000      1.5
  @@ -28,7 +28,7 @@
   children) processes.  You are looking for the parent process. If you
   run your server as root, you will easily locate it since it belongs to
   root. If you run the server as some other user (when you L<don't have
  -root access|guide::install/nstallation_Without_Superuser_Privileges>,
  +root access|guide::install/Installation_Without_Superuser_Privileges>,
   the processes will belong to that user unless defined differently in
   I<httpd.conf>.  It's still easy to find which is the parent--usually
   it's the process with the smallest PID.
  
  
  
  1.5       +1 -1      modperl-docs/src/docs/2.0/user/design/design.pod
  
  Index: design.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/design/design.pod,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- design.pod        27 Feb 2002 18:03:38 -0000      1.4
  +++ design.pod        28 Feb 2002 16:59:03 -0000      1.5
  @@ -21,7 +21,7 @@
   being implemented as a complete re-write from scratch.
   
   For a more detailed introduction and functionality overview, see
  -L<Overview|user::overview::overview/"test">.
  +L<Overview|user::overview::overview>.
   
   =head1 Interpreter Management
   
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to