From f9a7b967f5d48ee9c549e3fa2639720f64397b5b Mon Sep 17 00:00:00 2001 From: Chris Pepper Date: Wed, 28 Feb 2001 04:41:24 +0000 Subject: [PATCH] Adjusted links for files being moved into platform/ (were ./, now ../). Matched up

& 
. Fixed misspellings. Fixed links
 to ../install-tpf.html & ebcdic.html (which should probably be moved down
 into platform/). Changed links to windows.html#test to windows.html@cmdline.
 Entities encoded. Changed bogus  tags to .

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@88379 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/platform/netware.html       | 16 ++++----
 docs/manual/platform/perf-dec.html      |  9 +++--
 docs/manual/platform/readme-tpf.html    |  4 +-
 docs/manual/platform/win_compiling.html | 16 ++++----
 docs/manual/platform/win_service.html   | 16 ++++----
 docs/manual/platform/windows.html       | 49 +++++++++++++------------
 6 files changed, 57 insertions(+), 53 deletions(-)

diff --git a/docs/manual/platform/netware.html b/docs/manual/platform/netware.html
index c4939a756b..6e3aa68b0a 100644
--- a/docs/manual/platform/netware.html
+++ b/docs/manual/platform/netware.html
@@ -188,7 +188,7 @@ labeled as HTTPD_ROOT.
 Apache is configured by files in the conf
 directory. These are the same as files used to configure the Unix
 version, but there are a few different directives for Apache on
-NetWare. See the Apache documentation for all the
+NetWare. See the Apache documentation for all the
 available directives.
 
 

@@ -232,14 +232,14 @@ The main differences in Apache for NetWare are:
       without recompiling the server. If Apache is compiled normally, it
       will install a number of optional modules in the
       \Apache\modules directory. To activate these, or other
-      modules, the new LoadModule
+      modules, the new LoadModule
       directive must be used. For example, to active the status module,
       use the following (in addition to the status-activating directives
       in access.conf):

 
     LoadModule status_module modules/status
 

-      
Information on creating loadable
+      
Information on creating loadable
          modules is also available.

 
 
@@ -259,15 +259,15 @@ The main differences in Apache for NetWare are:
 
 
All major pieces of Apache may be built using the ApacheNW.mcp project
    file. This includes modules such as status, info, and proxy. In addition,
-   the following project files have been provided as well:
+   the following project files have been provided as well:

+
 
   
        /apache-1.3/src/support/htpasswd.mcp.gz
        /apache-1.3/src/support/htdigest.mcp.gz
 

 
-

-htpasswd.mcp.gz and htdigest.mcp.gz will also need
-to be unzipped before they can be used with MetroWerks CodeWarrior.
+
htpasswd.mcp.gz and htdigest.mcp.gz will also need
+to be unzipped before they can be used with MetroWerks CodeWarrior.

 
 
Once Apache has been compiled, it needs to be installed in its server
    root directory. The default is the sys:/Apache
@@ -277,7 +277,7 @@ Before running the server you must fill out the conf directory.
 Copy the *.conf-dist-nw from the distribution conf directory
 and rename *.conf.  Edit the ServerRoot entries to your
 actual server root (for example "sys:/apache").  Copy over
-the conf/magic and conf/mime.types files as well.
+the conf/magic and conf/mime.types files as well.

 
 
 
diff --git a/docs/manual/platform/perf-dec.html b/docs/manual/platform/perf-dec.html
index 2b9cc9cc5e..e2b8c30d2b 100644
--- a/docs/manual/platform/perf-dec.html
+++ b/docs/manual/platform/perf-dec.html
@@ -60,7 +60,7 @@ In article <skoogDs54BH.9pF@netcom.com> skoog@netcom.com (Jim Skoog) write
 >Where are the performance bottlenecks for Alpha AXP running the
 >Netscape Commerce Server 1.12 with high volume internet traffic?
 >We are evaluating network performance for a variety of Alpha AXP
->runing DEC UNIX 3.2C, which run DEC's seal firewall and behind
+>running DEC UNIX 3.2C, which run DEC's seal firewall and behind
 >that Alpha 1000 and 2100 webservers.
 
 Our experience (running such Web servers as 
 
 

 
-----------------------------------------------------------------------------
+
----------------------------------------------------------------------------
 
 From           mogul@pa.dec.com (Jeffrey Mogul)
 Organization   DEC Western Research
@@ -244,7 +245,7 @@ TUNING
         ipport_userreserved     The maximum number of concurrent non-reserved,
                                 dynamically allocated ports.  Default range
                                 is 1025-5000.  The maximum value is 65535.
-                                This limits the numer of times you can
+                                This limits the number of times you can
                                 simultaneously telnet or ftp out to connect
                                 to other systems.
 
@@ -278,8 +279,8 @@ inifaddr_hsize              -      X      X
 ipport_userreserved         -      X      -
 sysconfig -q inet           -      -      X
 sysconfig -q socket         -      -      X
-
 

+
 
 
 
diff --git a/docs/manual/platform/readme-tpf.html b/docs/manual/platform/readme-tpf.html
index 8bb0952193..6c89faee64 100644
--- a/docs/manual/platform/readme-tpf.html
+++ b/docs/manual/platform/readme-tpf.html
@@ -27,13 +27,13 @@ with care.
    (Transaction Processing Facility) operating system.
    Unless otherwise noted TPF version 4.1 PUT09 is required.
    


-   Refer to htdocs/manual/install-tpf.html
+   Refer to htdocs/manual/install-tpf.html
    for step-by-step installation instructions.
    


    As this is the first cut at making Apache run on TPF,
    performance tuning has not been done.
    


-   This port builds upon the EBCDIC changes
+   This port builds upon the EBCDIC changes
    previously made to Apache.
    

 

diff --git a/docs/manual/platform/win_compiling.html b/docs/manual/platform/win_compiling.html
index f1a2a71c89..0f854bea25 100644
--- a/docs/manual/platform/win_compiling.html
+++ b/docs/manual/platform/win_compiling.html
@@ -42,8 +42,8 @@
    information in the resulting files, making it easier to find bugs and
    track down problems.

 
-
Apache can also be compiled using VC++'s Visual Studio development
-   environment. To simplify this process, a Visual Studio workspace,
+
Apache can also be compiled using VC++'s VisualStudio development
+   environment. To simplify this process, a VisualStudio workspace,
    Apache.dsw, is provided.  This workspace exposes
    the entire list of working .dsp projects that are required for the
    complete Apache binary release.  It includes dependencies between
@@ -83,8 +83,8 @@
    
  • Apache.dsp requires ApacheCore and aprlibdll
 
 
-   In addition, the os\win32 subdirectory contains
-   project files for the optional modules.
+   
    In addition, the os\win32 subdirectory contains
+   project files for the optional modules.
    
 
 
      
   
    1. os\win32\ApacheModuleAuthAnon.dsp
@@ -101,7 +101,7 @@
   
    2. modules\proxy\ApacheModuleProxy.dsp
 
    
 
-   The support\ folder contains project files for additional
+   
    The support\ folder contains project files for additional
    programs that are not part of the apache runtime, but are used by
    the administrator to test Apache and maintain password and log files.
    
 
@@ -118,7 +118,7 @@
    directory, on the current hard drive. 
    
 
 
    To build and install all the files into the desired folder dir
-   automatically, use one the following nmake commands:
+   automatically, use one the following nmake commands:
    
 
 
      
   
    • nmake /f Makefile.win installr INSTDIR=dir
@@ -127,7 +127,7 @@
       (for debug build)
 
    
 
-   The dir argument to INSTDIR gives the installation directory; it 
+   
    The dir argument to INSTDIR gives the installation directory; it 
    can be omitted if Apache is to be installed into \Apache.
    
 
 
    This will install the following:
    
@@ -167,7 +167,7 @@
    reviewer's time.  Therefore, you cannot rely on the NMAKE commands 
    above to build revised .dsp project files unless you then export
    all .mak files yourself from the project.  This is unnecessary if 
-   you build from withing the Microsoft DeveloperStudio environment.
       
+   you build from within the Microsoft DeveloperStudio environment.
       
 
 
    Before running the server you must fill out the conf directory.
    Copy the *.conf-dist-win from the distribution conf directory
diff --git a/docs/manual/platform/win_service.html b/docs/manual/platform/win_service.html
index 6fb76bc9fd..de031beb6f 100644
--- a/docs/manual/platform/win_service.html
+++ b/docs/manual/platform/win_service.html
@@ -62,7 +62,7 @@
    details in the Windows NT Event Log.
    
 
 
    After starting Apache as a service (or if you have trouble starting it) 
-   you can test it using the same procedure
+   you can test it using the same procedure
    as for running in a console window.  Remember to use the command:
    
 
 
    @@ -168,8 +168,8 @@
 
 
    NEVER grant network privilages to the SYSTEM account!
    Create a new user account instead, grant the appropriate privilages to
-   that user, and use the the 'Log On As:' option.  Select the Start Menu ->
-   Settings -> Control Panel -> Services -> apache service ... and click 
+   that user, and use the the 'Log On As:' option.  Select the Start Menu ->
+   Settings -> Control Panel -> Services -> apache service ... and click 
    the "Startup" button to access this setting.
    
 
 
    
@@ -213,7 +213,7 @@
    a service with no problems.
    
 
    Note: error code 2186 is a good indication that you need 
    to review the 'Log On As' configuration, since the server can't access a 
-   required network resource.
    
+   required network resource.
    
 
 
 
    Troubleshooting Apache for Windows as a Service
    
@@ -227,7 +227,7 @@
 
    
 
    You will get this error if there is any problem starting Apache. In order to see
    what is causing the problem you should follow the instructions
-   for Testing Apache at the Command Prompt.
    
+   for Running Apache for Windows from the Command Line.
    
 
 
    Also, Apache 1.3.13 now records startup errors in the Application Event Log
    under Windows NT/2000, if Apache is run as a service.  Run the Event Viewer
@@ -288,19 +288,19 @@ For details on controlling Apache service from the command line, please refer to
    reliability or future support. Proceed at your own risk!
    
 
 
    Once you have confirmed that Apache runs correctly at the
-   Command Prompt you can install, control
+   Command Prompt you can install, control
    and uninstall it with the same commands as the Windows NT/2000 version.
    
 
 
    There are, however, significant differences that you should note:
    
 
 
    Apache will attempt to start and if successful it will run in the 
-   background.  If you run the command 
+   background.  If you run the command
    
 
 
        Apache -n "service name" -k start
 
    
 
-   via a shortcut on your desktop, for example, then if the service starts 
+   
    via a shortcut on your desktop, for example, then if the service starts 
    successfully a console window will flash up but immediately disappears.
    If Apache detects any errors  on startup such as a incorrect entries in the
    httpd.conf file, then the console window will remain visible. This will 
diff --git a/docs/manual/platform/windows.html b/docs/manual/platform/windows.html
index 9a52845a3c..325688ab6a 100644
--- a/docs/manual/platform/windows.html
+++ b/docs/manual/platform/windows.html
@@ -14,7 +14,7 @@
 >
 
 
-
    Using Apache With Microsoft Windows
    
+
    Using Apache with Microsoft Windows
    
 
 
    This document explains how to install, configure and run
    Apache 2.0 under Microsoft Windows. If you find any bugs, or wish 
@@ -56,7 +56,7 @@
    here.
    
 
 
    If running on NT 4.0, installing Service Pack 3 or 6 is recommended, as
-   Service Pack 4 created known issues with TCPIP/WinSock integrety that
+   Service Pack 4 created known issues with TCPIP/WinSock integrity that
    were resolved in later Service Packs.
    
 
 
    Warning: as of alpha 2.0a4 Windows 95 (and possibly 98) do not
@@ -227,7 +227,7 @@ There are two ways you can run Apache:
    service for Apache, first attempt to start it from the command
    line to assure that the service starts with no errors.
    
 
-
    Because Apache CANNOT share the same port with another
+
    Because Apache CANNOT share the same port with another
    TCPIP application, you may need to stop or uninstall certain 
    services first.  These include (but are not limited to) other
    web servers, and firewall products such as BlackIce.  If you can
@@ -240,7 +240,7 @@ There are two ways you can run Apache:
 
    Apache is configured by files in the conf
    directory. These are the same as files used to configure the Unix
    version, but there are a few different directives for Apache on
-   Windows. See the Apache documentation for all the
+   Windows. See the Apache documentation for all the
    available directives.
    
 
 
    The main differences in Apache for Windows are:
    
@@ -294,7 +294,7 @@ There are two ways you can run Apache:
   
  • Apache can also load ISAPI Extensions (i.e., Internet Server
          Applications), such as those used by Microsoft's IIS, and other
          Windows servers. More information
-         is available.  Note that Apache CANNOT load ISAPI
+         is available.  Note that Apache CANNOT load ISAPI
 		 Filters.
 
 
@@ -304,26 +304,26 @@ There are two ways you can run Apache:
    with Apache 1.3.7 and later.  Earlier versions of Apache only support
    the default service name 'Apache'.
    
 
-
    You can install Apache as a Windows NT service as follows:
+
    You can install Apache as a Windows NT service as follows:
    
 
 
         apache -k install -n "service name"
 
    
 
-  To install a service to use a particular configuration, specify the
-  configuration file when the service is installed:
+  
    To install a service to use a particular configuration, specify the
+  configuration file when the service is installed:
    
 
 
         apache -k install -n "service name" -f "\my server\conf\my.conf"
 
    
 
-  To remove an Apache service, use
+  
    To remove an Apache service, use
    
 
 
         apache -k uninstall -n "service name"
 
    
 
-  The default "service name", if one is not specified, is "Apache".
    
+  
    The default "service name", if one is not specified, is "Apache".
    
 
 
    Once a service is installed, you can use the -n option, in 
    conjunction with other options, to refer to a service's configuration 
@@ -386,19 +386,22 @@ There are two ways you can run Apache:
 
 
    When working with Apache it is important to know how it will find the
    configuration files.  You can specify a configuration file on the command line
-   in two ways:
+   in two ways:
    
 
 
      
-
    • -f specifies a path to a particular configuration file
+	
    • -f specifies a path to a particular configuration file
 
    
-
        apache -f "c:\my server\conf\my.conf"
    
-
        apache -f test\test.conf
    
+
+
        apache -f "c:\my server\conf\my.conf"
+    apache -f test\test.conf
    
+
 
      
-
    • -n specifies the configuration file of an installed Apache service (Apache 1.3.7 and later)
+	
    • -n specifies the configuration file of an installed Apache service (Apache 1.3.7 and later)
 
    
+
 
        apache -n "service name"
    
 
-   In these cases, the proper ServerRoot should be set in the configuration file.
    
+   
    In these cases, the proper ServerRoot should be set in the configuration file.
    
 
 
    If you don't specify a configuration file name with -f or -n, Apache will
    use the file name compiled into the server, usually "conf/httpd.conf".  Invoking
@@ -406,11 +409,11 @@ There are two ways you can run Apache:
    Apache will then determine its ServerRoot by trying the following, in this order:
    
 
 
      
-
    • A ServerRoot directive via a -C switch.
-
    • The -d switch on the command line.
-
    • Current working directory
-
    • A registry entry, created if you did a binary install.
-
    • The server root compiled into the server.
+	
    • A ServerRoot directive via a -C switch.
+	
    • The -d switch on the command line.
+	
    • Current working directory
+	
    • A registry entry, created if you did a binary install.
+	
    • The server root compiled into the server.
 
    
 
 
    The server root compiled into the server is usually "/apache".
@@ -450,13 +453,13 @@ There are two ways you can run Apache:
    directory in the httpd.conf file to the new location.
 
 
    To run Apache from the command line as a console application, use the
-   following command:
+   following command:
    
 
 
         apache 
 
    
 
-   Apache will execute, and will remain running until it is stopped by pressing
+   
    Apache will execute, and will remain running until it is stopped by pressing
    control-C.
    
 
 
    Signalling Service Apache when running
    
-- 
2.50.1