You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by er...@apache.org on 2002/08/29 21:08:15 UTC

cvs commit: httpd-2.0/docs/manual upgrading.xml upgrading.html.en

erikabele    2002/08/29 12:08:14

  Modified:    docs/manual upgrading.xml upgrading.html.en
  Log:
  Typo.
  
  Submitted by: Ilia Soldis <rk...@tversu.ru>
  
  Revision  Changes    Path
  1.2       +2 -2      httpd-2.0/docs/manual/upgrading.xml
  
  Index: upgrading.xml
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/upgrading.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- upgrading.xml	2 Aug 2002 12:13:14 -0000	1.1
  +++ upgrading.xml	29 Aug 2002 19:08:14 -0000	1.2
  @@ -131,7 +131,7 @@
   
         <li>The <code>AddModule</code> and
         <code>ClearModuleList</code> directives no longer exist.
  -      These directives where used to ensure that modules could be
  +      These directives were used to ensure that modules could be
         enabled in the correct order. The new Apache 2.0 API allows
         modules to explicitly specify their ordering, eliminating the
         need for these directives.</li>
  @@ -177,4 +177,4 @@
       Details are provided in the <a href="developer/">developer
       documentation</a>.</p>
     </section>
  -</manualpage>
  \ No newline at end of file
  +</manualpage>
  
  
  
  1.26      +1 -1      httpd-2.0/docs/manual/upgrading.html.en
  
  Index: upgrading.html.en
  ===================================================================
  RCS file: /home/cvs/httpd-2.0/docs/manual/upgrading.html.en,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- upgrading.html.en	14 Aug 2002 18:56:00 -0000	1.25
  +++ upgrading.html.en	29 Aug 2002 19:08:14 -0000	1.26
  @@ -117,7 +117,7 @@
   
         <li>The <code>AddModule</code> and
         <code>ClearModuleList</code> directives no longer exist.
  -      These directives where used to ensure that modules could be
  +      These directives were used to ensure that modules could be
         enabled in the correct order. The new Apache 2.0 API allows
         modules to explicitly specify their ordering, eliminating the
         need for these directives.</li>