perl-docs-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject cvs commit: modperl-docs/src/docs/1.0/guide Changes.pod dbm.pod install.pod intro.pod method_handlers.pod performance.pod porting.pod scenario.pod
Date Tue, 14 Sep 2004 18:12:03 GMT
stas        2004/09/14 11:12:03

  Modified:    src/docs/1.0/guide Changes.pod dbm.pod install.pod intro.pod
                        method_handlers.pod performance.pod porting.pod
                        scenario.pod
  Log:
  various language corrections
  Submitted by:	Richard Morin <rdm@slac.stanford.edu>
  
  Revision  Changes    Path
  1.41      +6 -1      modperl-docs/src/docs/1.0/guide/Changes.pod
  
  Index: Changes.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/Changes.pod,v
  retrieving revision 1.40
  retrieving revision 1.41
  diff -u -u -r1.40 -r1.41
  --- Changes.pod	12 Apr 2004 19:08:06 -0000	1.40
  +++ Changes.pod	14 Sep 2004 18:12:02 -0000	1.41
  @@ -5,11 +5,16 @@
   =head1 Description
   
   Refer to this document to learn what changes were made to the
  -documents, since you've read these last time. 
  +documents, since you've read these last time.
   
   The most recent changes are listed first.
   
   =head1 Ongoing
  +
  +* misc
  +
  + o various language corrections from Richard Morin <rdm /at/
  + slac.stanford.edu>
   
   * scenario.pod:
   
  
  
  
  1.8       +1 -1      modperl-docs/src/docs/1.0/guide/dbm.pod
  
  Index: dbm.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/dbm.pod,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -u -r1.7 -r1.8
  --- dbm.pod	3 Apr 2002 09:16:08 -0000	1.7
  +++ dbm.pod	14 Sep 2004 18:12:02 -0000	1.8
  @@ -5,7 +5,7 @@
   =head1 Description
   
   Small databases can be implemented pretty efficiently using dbm files,
  -but there are still some precautions that must be taken to use
  +but there are still some precautions that must be taken to use them
   properly under mod_perl.
   
   =head1 Where and Why to use dbm files
  
  
  
  1.28      +2 -2      modperl-docs/src/docs/1.0/guide/install.pod
  
  Index: install.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/install.pod,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -u -r1.27 -r1.28
  --- install.pod	6 Aug 2004 23:50:05 -0000	1.27
  +++ install.pod	14 Sep 2004 18:12:02 -0000	1.28
  @@ -5,8 +5,8 @@
   =head1 Description
   
   An in-depth explanation of the mod_perl installation process, from the
  -basic installation in 10 steps, to more complex one with all the
  -possible options you might want to use, including DSO build. It
  +basic installation (in 10 steps), to a more complex one (with all the
  +possible options you might want to use, including DSO build). It
   includes troubleshooting tips too.
   
   First of all:
  
  
  
  1.18      +11 -10    modperl-docs/src/docs/1.0/guide/intro.pod
  
  Index: intro.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/intro.pod,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -u -r1.17 -r1.18
  --- intro.pod	30 Sep 2003 18:07:00 -0000	1.17
  +++ intro.pod	14 Sep 2004 18:12:02 -0000	1.18
  @@ -6,16 +6,16 @@
   
   An introduction to what mod_perl is all about, its different features,
   and some explanations of the C API, C<Apache::Registry>,
  -C<Apache::PerlRun> and the Apache/Perl API.
  +C<Apache::PerlRun>, and the Apache/Perl API.
   
   
   =head1 What is mod_perl?
   
   The Apache/Perl integration project brings together the full power of
   the Perl programming language and the Apache HTTP server. With
  -mod_perl it is possible to write Apache modules entirely in Perl,
  -letting you easily do things that are more difficult or impossible in
  -regular CGI programs, such as running sub requests. In addition, the
  +mod_perl, it is possible to write Apache modules entirely in Perl,
  +letting you easily do things (such as running sub-requests) that are
  +more difficult or impossible in regular CGI programs. In addition, the
   persistent Perl interpreter embedded in the server saves the overhead
   of starting an external interpreter, i.e. the penalty of Perl start-up
   time.  And not the least important feature is code caching, where
  @@ -26,7 +26,7 @@
   
   The primary advantages of mod_perl are power and speed. You have full
   access to the inner workings of the web server and can intervene at
  -any stage of request-processing. This allows for customized processing
  +any stage of request processing. This allows for customized processing
   of (to name just a few of the phases) URI-E<gt>filename translation,
   authentication, response generation, and logging. There is very little
   run-time overhead. In particular, it is not necessary to start a
  @@ -58,14 +58,15 @@
   
     ScriptAlias /cgi-bin/ /home/httpd/cgi-bin/
   
  -you run it under a mod_cgi handler, you never define it
  -explicitly. Apache does all the configuration work behind the scenes,
  -when you use a ScriptAlias.
  +you are running them under a mod_cgi handler, although you never
  +define it explicitly. Apache does all the configuration work behind
  +the scenes, when you use a ScriptAlias.
   
   By the way, don't confuse C<ScriptAlias> with the C<ExecCGI>
   configuration option, which we enable so that the script will be
   executed rather than returned as a plain text file. For example for
  -mod_perl and C<Apache::Registry> you would use a configuration like:
  +mod_perl and C<Apache::Registry> you would use a configuration such
  +as:
   
     <Location /perl>
       SetHandler perl-script
  @@ -77,7 +78,7 @@
   =head2 C API
   
   The Apache C API has been present for a long time, and has been the
  -usual way to program extensions to Apache, such as mod_perl. When you
  +usual way to program extensions (such as mod_perl) to Apache. When you
   write C extension modules, you write C code that is not independent,
   but will be linked into the Apache I<httpd> executable either at build
   time (if the module is statically linked), or at runtime (if it is
  
  
  
  1.5       +3 -3      modperl-docs/src/docs/1.0/guide/method_handlers.pod
  
  Index: method_handlers.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/method_handlers.pod,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -u -r1.4 -r1.5
  --- method_handlers.pod	12 Jan 2004 08:33:39 -0000	1.4
  +++ method_handlers.pod	14 Sep 2004 18:12:02 -0000	1.5
  @@ -1,11 +1,11 @@
  -=head1 NAME 
  +=head1 NAME
   
   How to use mod_perl's Method Handlers
   
   =head1 Description
   
  -Described here are a few examples and hints how to use MethodHandlers
  -with mod_perl.
  +Described here are a few examples and hints on how to use method
  +handlers with mod_perl.
   
   This document assumes familiarity with at least the I<perltoot>
   manpage and "normal" usage of the C<Perl*Handlers>.
  
  
  
  1.30      +1 -1      modperl-docs/src/docs/1.0/guide/performance.pod
  
  Index: performance.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/performance.pod,v
  retrieving revision 1.29
  retrieving revision 1.30
  diff -u -u -r1.29 -r1.30
  --- performance.pod	4 Jul 2004 03:51:40 -0000	1.29
  +++ performance.pod	14 Sep 2004 18:12:02 -0000	1.30
  @@ -6,7 +6,7 @@
   
   An exhaustive list of various techniques you might want to use to get
   the most performance possible out of your mod_perl server:
  -configuration, coding, memory use and more.
  +configuration, coding, memory use, and more.
   
   =head1 The Big Picture
   
  
  
  
  1.22      +2 -2      modperl-docs/src/docs/1.0/guide/porting.pod
  
  Index: porting.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/porting.pod,v
  retrieving revision 1.21
  retrieving revision 1.22
  diff -u -u -r1.21 -r1.22
  --- porting.pod	9 Jun 2004 09:13:48 -0000	1.21
  +++ porting.pod	14 Sep 2004 18:12:02 -0000	1.22
  @@ -4,8 +4,8 @@
   
   =head1 Description
   
  -This chapter is relevant to both writing a new CGI script or perl
  -handler from scratch and migrating an application from plain CGI to
  +This chapter is relevant both to writing a new CGI script or perl
  +handler from scratch and to migrating an application from plain CGI to
   mod_perl.
   
   It also addresses the situation where the CGI script being ported does
  
  
  
  1.11      +4 -3      modperl-docs/src/docs/1.0/guide/scenario.pod
  
  Index: scenario.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/1.0/guide/scenario.pod,v
  retrieving revision 1.10
  retrieving revision 1.11
  diff -u -u -r1.10 -r1.11
  --- scenario.pod	22 Dec 2003 02:24:22 -0000	1.10
  +++ scenario.pod	14 Sep 2004 18:12:02 -0000	1.11
  @@ -4,10 +4,11 @@
   
   =head1 Description
   
  -This chapter provides step by step installation guide for the various
  -setups discussed in L<Choosing the Right Strategy|guide::strategy>.
  +This chapter provides a step-by-step installation guide for the
  +various setups discussed in L<Choosing the Right
  +Strategy|guide::strategy>.
   
  -=head1 Assumptions 
  +=head1 Assumptions
   
   I will assume for this section that you are familiar with plain (not
   mod_perl enabled) Apache, its compilation and configuration. In all
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org


Mime
View raw message