httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From m...@hyperreal.org
Subject cvs commit: apachen/htdocs/manual/vhosts details.html examples.html
Date Mon, 29 Dec 1997 20:41:56 GMT
marc        97/12/29 12:41:56

  Modified:    htdocs/manual new_features_1_3.html sections.html
                        sourcereorg.html
               htdocs/manual/misc perf-hp.html vif-info.html
                        windoz_keepalive.html
               htdocs/manual/mod mod_alias.html mod_example.html
                        mod_imap.html mod_isapi.html mod_speling.html
               htdocs/manual/vhosts details.html examples.html
  Log:
  Misc spelling fixes.
  
  PR: 1600
  Submitted by:	 "Daniel S.Lewart" <d-lewart@uiuc.edu>
  
  Revision  Changes    Path
  1.37      +2 -2      apachen/htdocs/manual/new_features_1_3.html
  
  Index: new_features_1_3.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/new_features_1_3.html,v
  retrieving revision 1.36
  retrieving revision 1.37
  diff -u -r1.36 -r1.37
  --- new_features_1_3.html	1997/12/16 22:03:02	1.36
  +++ new_features_1_3.html	1997/12/29 20:41:46	1.37
  @@ -160,7 +160,7 @@
   </LI>
   <li><STRONG><a href="windows.html">Support for Windows NT/95</a></STRONG><br>
   Apache now supports the Windows NT and Windows 95 operating systems,
  -as well as the Unix systems supported in previos releases. Although the
  +as well as the Unix systems supported in previous releases. Although the
   Windows version of Apache may not be perform as well as on the Unix
   systems for which Apache was originally written, the ability to run on
   Windows gives Apache the ability to run on a large number of web
  @@ -225,7 +225,7 @@
   <li><strong><SAMP>HostNameLookups</SAMP> now defaults to "Off"</strong><br>
       The <a
       href="mod/core.html#hostnamelookups"><SAMP>HostNameLookups</SAMP></a>
  -    directive now defaults to "Off". This means that, unless explictly
  +    directive now defaults to "Off". This means that, unless explicitly
       turned on, the server will not resolve IP addresses into names. This
       was done to spare the Internet from unnecessary DNS traffic.
   
  
  
  
  1.3       +1 -1      apachen/htdocs/manual/sections.html
  
  Index: sections.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/sections.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- sections.html	1997/11/11 23:10:45	1.2
  +++ sections.html	1997/12/29 20:41:47	1.3
  @@ -117,7 +117,7 @@
   </ul>
   
   Note also that modifying .htaccess parsing during Location doesn't do
  -anything because .htaccess parsing has already occured.
  +anything because .htaccess parsing has already occurred.
   
   <p>
   
  
  
  
  1.6       +5 -5      apachen/htdocs/manual/sourcereorg.html
  
  Index: sourcereorg.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/sourcereorg.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- sourcereorg.html	1997/09/12 09:27:31	1.5
  +++ sourcereorg.html	1997/12/29 20:41:47	1.6
  @@ -105,7 +105,7 @@
   
   In previous releases of Apache, new modules were added to the
   <CODE>src</CODE> directory, and if the module required any additional
  -compilation options (such as libaries) they would have to be added
  +compilation options (such as libraries) they would have to be added
   to <CODE>Configuration</CODE>. Also the user would have to be
   told the module's structure name to add on the Module line
   of <CODE>Configuration</CODE>.
  @@ -138,7 +138,7 @@
   The rest of this document shows how to package modules for Apache 1.3
   and later and what to tell end-users of the module.
   
  -<h3>Building a simple source distibution</h3>
  +<h3>Building a simple source distribution</h3>
   
   Consider a simple add-on module, distributed as a single file. For
   example, say it is called mod_demo.c. The archive for this module
  @@ -175,7 +175,7 @@
   
   When the user runs <CODE>Configure</CODE> Apache will create a full
   makefile to build this module. If this module also requires
  -some additional built-time options to be given, such as libaries,
  +some additional built-time options to be given, such as libraries,
   see the next section.
   <P>
   
  @@ -250,10 +250,10 @@
   
   <h3>Module Definition Information for Binary Distribitions</h3>
   
  -If the module is to be distributed as binary (object or libary) rather
  +If the module is to be distributed as binary (object or library) rather
   than source, it is not possible to add the module definition
   information to the source file. In this case it can be placed in a
  -separate file which has the same base name as the object or libary
  +separate file which has the same base name as the object or library
   file, but with a <CODE>.module</CODE> extension. So, for example, if
   the distributed module object file is mod_demo.o, the module
   definition file should be called mod_demo.module. It contains the same
  
  
  
  1.2       +1 -1      apachen/htdocs/manual/misc/perf-hp.html
  
  Index: perf-hp.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/misc/perf-hp.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- perf-hp.html	1997/11/06 02:55:08	1.1
  +++ perf-hp.html	1997/12/29 20:41:49	1.2
  @@ -74,7 +74,7 @@
   If folks are running Apache on a PA-8000 based system, they should
   consider "chatr'ing" the Apache executable to have a large page size.
   This would be "chatr +pi L <binary>." The GID of the running executable
  -must have MLOCK priviledges. Setprivgrp(1m) should be consulted for
  +must have MLOCK privileges. Setprivgrp(1m) should be consulted for
   assigning MLOCK. The change can be validated by running Glance and
   examining the memory regions of the server(s) to make sure that they
   show a non-trivial fraction of the text segment being locked.
  
  
  
  1.9       +1 -1      apachen/htdocs/manual/misc/vif-info.html
  
  Index: vif-info.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/misc/vif-info.html,v
  retrieving revision 1.8
  retrieving revision 1.9
  diff -u -r1.8 -r1.9
  --- vif-info.html	1997/07/06 17:19:08	1.8
  +++ vif-info.html	1997/12/29 20:41:49	1.9
  @@ -366,7 +366,7 @@
   
   This will cause the device to be opened, which will if_attach the
   interfaces. If you feel like playing with the code, you may want to
  -kmem_alloc() the vif_softc structrure at open time, and use the minor
  +kmem_alloc() the vif_softc structure at open time, and use the minor
   number of the device to tell it how many interfaces to create.
   
   Now you can go ahead and ifconfig etc.
  
  
  
  1.4       +1 -1      apachen/htdocs/manual/misc/windoz_keepalive.html
  
  Index: windoz_keepalive.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/misc/windoz_keepalive.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- windoz_keepalive.html	1997/06/04 11:42:59	1.3
  +++ windoz_keepalive.html	1997/12/29 20:41:50	1.4
  @@ -28,7 +28,7 @@
   1) On Netscape 3.0b4, I was able to reproduce the bug, each and every
   time. It's really simple: go to the Network Setup panel. Set it to
   "Connect Every Time" and only let it have 1 connection at once (this may
  -not be neccessary, but it's helpeful). Then load an image that's
  +not be necessary, but it's helpful). Then load an image that's
   kept-alive. Then wait until the connection times out (this depends on the
   server - 10-30 seconds, except for MIIS, which never times out, near as I
   can tell). Then hit reload. It will hang. (actually, once it crashed).
  
  
  
  1.15      +3 -3      apachen/htdocs/manual/mod/mod_alias.html
  
  Index: mod_alias.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/mod/mod_alias.html,v
  retrieving revision 1.14
  retrieving revision 1.15
  diff -u -r1.14 -r1.15
  --- mod_alias.html	1997/12/07 23:03:45	1.14
  +++ mod_alias.html	1997/12/29 20:41:51	1.15
  @@ -76,7 +76,7 @@
   <strong>Compatibility:</strong> Available in Apache 1.3 and later
   </P>
   
  -<p>This directive is equivilent to <a href="#alias">Alias</a>, but
  +<p>This directive is equivalent to <a href="#alias">Alias</a>, but
   makes use of standard regular expressions, instead of simple prefix
   matching. The supplied regular expression is matched against the URL,
   and if it matches, the server will substitute any parenthesized
  @@ -162,7 +162,7 @@
   <strong>Compatibility:</strong> Available in Apache 1.3 and later
   </P>
   
  -<p>This directive is equivilent to <a href="#alias">Redirect</a>, but
  +<p>This directive is equivalent to <a href="#alias">Redirect</a>, but
   makes use of standard regular expressions, instead of simple prefix
   matching. The supplied regular expression is matched against the URL,
   and if it matches, the server will substitute any parenthesized
  @@ -241,7 +241,7 @@
   <strong>Compatibility:</strong> Available in Apache 1.3 and later
   </P>
   
  -<p>This directive is equivilent to <a href="#scriptalias">ScriptAlias</a>,
but
  +<p>This directive is equivalent to <a href="#scriptalias">ScriptAlias</a>,
but
   makes use of standard regular expressions, instead of simple prefix
   matching. The supplied regular expression is matched against the URL,
   and if it matches, the server will substitute any parenthesized
  
  
  
  1.6       +1 -1      apachen/htdocs/manual/mod/mod_example.html
  
  Index: mod_example.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/mod/mod_example.html,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- mod_example.html	1997/10/15 14:45:25	1.5
  +++ mod_example.html	1997/12/29 20:41:51	1.6
  @@ -32,7 +32,7 @@
     </P>
     <P>
     The main file is <CODE>mod_example.c</CODE>, which illustrates all
  -  the different callback mechanisms and call syntaces.  By no means does
  +  the different callback mechanisms and call syntaxes.  By no means does
     an add-on module need to include routines for all of the callbacks -
     quite the contrary!
     </P>
  
  
  
  1.8       +1 -1      apachen/htdocs/manual/mod/mod_imap.html
  
  Index: mod_imap.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/mod/mod_imap.html,v
  retrieving revision 1.7
  retrieving revision 1.8
  diff -u -r1.7 -r1.8
  --- mod_imap.html	1997/07/06 17:19:17	1.7
  +++ mod_imap.html	1997/12/29 20:41:52	1.8
  @@ -272,7 +272,7 @@
   
   <h2>Referencing your mapfile</h2>
   <blockquote><code>
  -&lt;A HREF="/maps/imagmap1.map"&gt; <br>
  +&lt;A HREF="/maps/imagemap1.map"&gt; <br>
   &lt;IMG ISMAP SRC="/images/imagemap1.gif"&gt; <br>
   &lt;/A&gt;
   </code></blockquote><p>
  
  
  
  1.2       +1 -1      apachen/htdocs/manual/mod/mod_isapi.html
  
  Index: mod_isapi.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/mod/mod_isapi.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- mod_isapi.html	1997/07/22 20:47:40	1.1
  +++ mod_isapi.html	1997/12/29 20:41:52	1.2
  @@ -47,7 +47,7 @@
   
   <p>Apache's ISAPI implementation conforms to all of the ISAPI 2.0
      specification, except for the "Microsoft-specific" extensions dealing
  -   with ascynchronous I/O. Apache's I/O model does not allow asynchronous
  +   with asynchronous I/O. Apache's I/O model does not allow asynchronous
      reading and writing in a manner that the ISAPI could access. If an ISA
      tries to access async I/O, a message will be place in the error log,
      to help with debugging.
  
  
  
  1.3       +2 -2      apachen/htdocs/manual/mod/mod_speling.html
  
  Index: mod_speling.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/mod/mod_speling.html,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- mod_speling.html	1997/11/12 16:29:46	1.2
  +++ mod_speling.html	1997/12/29 20:41:53	1.3
  @@ -16,7 +16,7 @@
     <P>
     This module is contained in the <code>mod_speling.c</code> file,
     and is <strong>not</strong> compiled in by default.
  -  It attemps to correct misspellings of
  +  It attempts to correct misspellings of
     URLs that users might have entered, by ignoring capitalization
     and by allowing up to one misspelling.<br>
     This catches the majority of misspelled requests. An automatic
  @@ -76,7 +76,7 @@
         correction will have an impact on the server's performance
         when many spelling corrections have to be performed at the same time.
     <LI>the document trees should not contain sensitive files which could
  -      be matched inadvertedly, by a spelling "correction".
  +      be matched inadvertently, by a spelling "correction".
     <LI>the module is unable to correct misspelled user names
         (as in <code>http://my.host/~apahce/</code>), just file names or
         directory names.
  
  
  
  1.2       +1 -1      apachen/htdocs/manual/vhosts/details.html
  
  Index: details.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/vhosts/details.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- details.html	1997/11/11 23:47:18	1.1
  +++ details.html	1997/12/29 20:41:54	1.2
  @@ -299,7 +299,7 @@
       
   <li>A <code>_default_</code> vhost catches a request only if there is
no
       other vhost with a matching IP address <em>and</em> a matching port
  -    number for the request. The request is only catched if the port number
  +    number for the request. The request is only caught if the port number
       to which the client sent the request matches the port number of your
       <code>_default_</code> vhost which is your standard <code>Port</code>
       by default. A wildcard port can be specified (i.e.
  
  
  
  1.2       +2 -2      apachen/htdocs/manual/vhosts/examples.html
  
  Index: examples.html
  ===================================================================
  RCS file: /export/home/cvs/apachen/htdocs/manual/vhosts/examples.html,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- examples.html	1997/11/11 23:47:19	1.1
  +++ examples.html	1997/12/29 20:41:55	1.2
  @@ -91,7 +91,7 @@
       ...
       &lt;/VirtualHost&gt;
       </pre>
  -    The main server can never catch a request, because all IP address
  +    The main server can never catch a request, because all IP addresses
       of our machine are in use for IP-based virtual hosts
       (only <samp>localhost</samp> requests can hit the main server).
       </blockquote>
  @@ -134,7 +134,7 @@
         &lt;/Directory&gt;
       &lt;/VirtualHost&gt;
       </pre>
  -    The main server can never catch a request, because all IP addresss
  +    The main server can never catch a request, because all IP addresses
       (apart from <samp>localhost</samp>) of our machine are in use for IP-based
       virtual hosts. The web server can only be reached on the first address
       through port 80 and the proxy only on the second address through port 8080.
  
  
  

Mime
View raw message