From: Joshua Slive <slive@apache.org>
Date: Sun, 29 Jun 2003 19:35:28 +0000 (+0000)
Subject: Just some small gramatical improvements.
X-Git-Tag: pre_ajp_proxy~1496
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=106dd1058c48212af972036d99ac4a02df0d4eb0;p=apache

Just some small gramatical improvements.


git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@100402 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml
index 3e0c3425d0..73826e48c3 100644
--- a/docs/manual/mod/core.xml
+++ b/docs/manual/mod/core.xml
@@ -2446,7 +2446,7 @@ later</compatibility>
       #!C:/Perl/bin/perl.exe
     </example>
 
-    <p>or, if perl is in <code>PATH</code>, simply:</p>
+    <p>or, if perl is in the <code>PATH</code>, simply:</p>
 
     <example>
       #!perl
@@ -2456,29 +2456,32 @@ later</compatibility>
     cause the Windows Registry tree <code>HKEY_CLASSES_ROOT</code> to be
     searched using the script file extension (e.g., <code>.pl</code>) as a
     search key. The command defined by the registry subkey
-    <code>Shell\ExecCGI\Command</code> or if not exists by the subkey
-    <code>Shell\Open\Command</code> is used to open the script file. In absence
-    of the file extension key or both subkeys Apache uses the
+    <code>Shell\ExecCGI\Command</code> or, if it does not exist, by the subkey
+    <code>Shell\Open\Command</code> is used to open the script file. If the
+    registry keys cannot be found, Apache falls back to the behavior of the
     <code>Script</code> option.</p>
 
-    <note type="warning"><title>Security</title>
-      <p>Be careful to use <code>ScriptInterpreterSource Registry</code> with 
-      <directive module="mod_alias">ScriptAlias</directive>'ed directories,
-      because Apache is trying to execute <strong>every</strong> file within
-      this directory. The <code>Registry</code> setting may cause undesired
-      program calls on files, which are usually not executed. For example, the
-      default open command on <code>.htm</code> files on most Windows systems is
-      executing the Microsoft Internet Explorer, so any HTTP request for an
-      <code>.htm</code> file existing within the script directory would start
-      the browser in background. This is an effective method to crash your
-      system within a minute or so.</p>
+    <note type="warning"><title>Security</title> 
+    <p>Be careful when using <code>ScriptInterpreterSource
+    Registry</code> with <directive
+    module="mod_alias">ScriptAlias</directive>'ed directories, because
+    Apache will try to execute <strong>every</strong> file within this
+    directory. The <code>Registry</code> setting may cause undesired
+    program calls on files which are typically not executed. For
+    example, the default open command on <code>.htm</code> files on
+    most Windows systems will execute Microsoft Internet Explorer, so
+    any HTTP request for an <code>.htm</code> file existing within the
+    script directory would start the browser in the background on the
+    server. This is a good way to crash your system within a minute or
+    so.</p>
     </note>
 
-    <p>The option <code>Registry-Strict</code> which is new in Apache 2.0
-      does the same as <code>Registry</code> but uses only the subkey
-      <code>Shell\ExecCGI\Command</code>. The <code>ExecCGI</code> key
-      is not a common one. It has to be configured manually and prevents your
-      system from accidental program calls.</p>
+    <p>The option <code>Registry-Strict</code> which is new in Apache
+    2.0 does the same thing as <code>Registry</code> but uses only the
+    subkey <code>Shell\ExecCGI\Command</code>. The
+    <code>ExecCGI</code> key is not a common one. It must be
+    configured manually in the windows registry and hence prevents
+    accidental program calls on your system.</p>
 </usage>
 </directivesynopsis>