From: Daniel Gruno <humbedooh@apache.org>
Date: Fri, 20 Apr 2012 10:21:57 +0000 (+0000)
Subject: xforms
X-Git-Tag: 2.4.3~548
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=7dd32bed0ad25c9aa4919fdb8818480c23e53d1f;p=apache

xforms

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1328300 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/docs/manual/mod/event.html.en b/docs/manual/mod/event.html.en
index 25b89774b7..fa2b2f2a5a 100644
--- a/docs/manual/mod/event.html.en
+++ b/docs/manual/mod/event.html.en
@@ -82,7 +82,7 @@ of consuming threads only for connections with active processing</td></tr>
     <p>This MPM tries to fix the 'keep alive problem' in HTTP. After a client
     completes the first request, the client can keep the connection
     open, and send further requests using the same socket. This can
-    save signifigant overhead in creating TCP connections. However,
+    save significant overhead in creating TCP connections. However,
     Apache HTTP Server traditionally keeps an entire child process/thread waiting
     for data from the client, which brings its own disadvantages. To
     solve this problem, this MPM uses a dedicated thread to handle both
@@ -150,7 +150,7 @@ of consuming threads only for connections with active processing</td></tr>
     needed, and other (mostly SSL) connections with one request worker thread
     reserved per connection. This can lead to situations where all workers are
     tied up and no worker thread is available to handle new work on established
-    async connetions.</p>
+    async connections.</p>
 
     <p>To mitigate this problem, the event MPM does two things: Firstly, it
     limits the number of connections accepted per process, depending on the