From: Daniel Gruno <humbedooh@apache.org>
Date: Sun, 5 Aug 2012 22:24:17 +0000 (+0000)
Subject: Fix some typos and wordings
X-Git-Tag: 2.5.0-alpha~6497
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=284dc4ee6ccf69b0552b8fad91bd1fe86435a8da;p=thirdparty%2Fapache%2Fhttpd.git

Fix some typos and wordings

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

diff --git a/docs/manual/mod/mod_lua.xml b/docs/manual/mod/mod_lua.xml
index dbeec108100..03afd9f01e4 100644
--- a/docs/manual/mod/mod_lua.xml
+++ b/docs/manual/mod/mod_lua.xml
@@ -649,8 +649,8 @@ end
 
     <dt>server:</dt>  <dd>This one is different than others because the
             server scope is quite long lived, and multiple threads
-            will have the same server_rec. To accommodate this
-            server scoped interpreter are stored in an apr
+            will have the same server_rec. To accommodate this,
+            server scoped Lua states are stored in an apr
             resource list. The <code>min</code> and <code>max</code> arguments 
             specify the minimum and maximum number of Lua states to keep in the 
             pool.</dd>
@@ -665,7 +665,7 @@ end
     maximum performance. While the <code>thread</code> scope will provide the 
     fastest responses, the <code>server</code> scope will use less memory, as 
     states are pooled, allowing f.x. 1000 threads to share only 100 Lua states, 
-    thus using only 10% of the memory requried by the <code>thread</code> scope.
+    thus using only 10% of the memory required by the <code>thread</code> scope.
     </p>
 </usage>
 </directivesynopsis>
@@ -682,8 +682,8 @@ end
     <p>This directive matches a uri pattern to invoke a specific
     handler function in a specific file. It uses PCRE regular
     expressions to match the uri, and supports interpolating
-    match groups into both the file path and the function name
-    be careful writing your regular expressions to avoid security
+    match groups into both the file path and the function name. 
+    Be careful writing your regular expressions to avoid security
     issues.</p>
    <example><title>Examples:</title>
    <highlight language="config">