> Oh darn... but here comes a diff between two Unix versions of the > file. :-)
It's very easy to read. Nice work. I've only some small suggestions. Could you check them and send a further patch? I'll commit this if Bill Rowe or others have no further comments. Section "Customizing Apache for Windows": 1) ... See the Apache documentation for all the available directives. -> ... See the directive index for all the available directives. and link directly to this file. Section "Running Apache as a service": 2) <p>By default, all Apache services are registered to run as user <code>System</code> (the LocalSystem account). The <code>System </code> account has no privileges to your network via any Windows-secured mechanism, including the file system, named pipes, DCOM, or secure RPC. It has, however, wide privileges locally.</p> Do note mark "system" as code, because the account name is not "System" but "LocalSystem". Ok, this is only a little markup issue. Probaly you want to write: -> <p>By default, all Apache services are registered to run as system user (the <code>LocalSystem</code> account). The <code>LocalSystem </code> account has no privileges to your network via any Windows-secured mechanism, including the file system, named pipes, DCOM, or secure RPC. It has, however, wide privileges locally.</p> Section "Running Apache as a Consol� Application": 3) You can also run Apache via the shortcut Start Apache in Console placed to Start Menu --> Programs --> Apache HTTP Server 2.0.xx --> Control Apache Server during the installation. This will open a console window and start Apache inside it. The window will remain visible until you stop Apache. The Windows stays open only if Apache is not installed as a service. Otherwise this menu entry starts the service and closes the console window. (Tested on Windows 2000) 4) If you don't specify a configuration file with -f or -n, Apache will use the file name compiled into the server, such as conf\httpd.conf, relative to the path specified by the ServerRoot directive. Maybe I'm missing something. But the sentence is mistakable. One could read: the configuration file is relative to the ServerRoot directive. This could never be because the configuration file must be found and read before apache is able to notice the ServerRoot directive. 5) You are often using <li><p>....</p></li>. Is this intended? Imho <li>... </li> is also ok. Section "Testing the Installation": 6) After starting Apache (either in a console window or as a service) it will be listening on port 80 (unless you changed the Listen directive in the configuration files). -> After starting Apache (either in a console window or as a service) it will be listening on port 80 (unless you changed the Listen directive in the configuration files or installed apache only for the current user).
