From 817292c5e763f26dd54d048f77c4d5ae26e9abe4 Mon Sep 17 00:00:00 2001
From: Luca Toscano <elukey@apache.org>
Date: Fri, 12 Feb 2016 07:41:06 +0000
Subject: [PATCH] Documentation rebuild.

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1729950 13f79535-47bb-0310-9956-ffa450edef68
---
 docs/manual/mod/event.html.en | 12 ++++--------
 docs/manual/mod/event.xml.fr  |  2 +-
 2 files changed, 5 insertions(+), 9 deletions(-)

diff --git a/docs/manual/mod/event.html.en b/docs/manual/mod/event.html.en
index 7a6ddcb550..f1b03f225c 100644
--- a/docs/manual/mod/event.html.en
+++ b/docs/manual/mod/event.html.en
@@ -142,16 +142,12 @@ of the <code class="directive">AsyncRequestWorkerFactor</code>.</p>
         All modules shipped with the server are compatible with the event MPM.</p>
 
         <p>A similar restriction is currently present for requests involving an
-        output filter that needs to read and/or modify the whole response body,
-        like for example mod_ssl, mod_deflate, or mod_include. If the
-        connection to the client blocks while the filter is processing the
+        output filter that needs to read and/or modify the whole response body. 
+        If the connection to the client blocks while the filter is processing the
         data, and the amount of data produced by the filter is too big to be
         buffered in memory, the thread used for the request is not freed while
-        httpd waits until the pending data is sent to the client. Please note that
-        this limitation is only a corner case, it does not mean that the event MPM
-        defaults to worker in presence of TLS/SSL connections and/or compression.</p> 
-        
-        <p>To illustrate this point we can think about the following two situations: 
+        httpd waits until the pending data is sent to the client.<br /> 
+        To illustrate this point we can think about the following two situations: 
         serving a static asset (like a CSS file) versus serving content retrieved from
         FCGI/CGI or a proxied server. The former is predictable, namely the event MPM 
         has full visibility on the end of the content and it can use events: the worker 
diff --git a/docs/manual/mod/event.xml.fr b/docs/manual/mod/event.xml.fr
index afeca05198..9277c9df72 100644
--- a/docs/manual/mod/event.xml.fr
+++ b/docs/manual/mod/event.xml.fr
@@ -1,7 +1,7 @@
 <?xml version="1.0"?>
 <!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
 <?xml-stylesheet type="text/xsl" href="../style/manual.fr.xsl"?>
-<!-- English Revision: 1515476:1729748 (outdated) -->
+<!-- English Revision: 1515476:1729949 (outdated) -->
 <!-- French translation : Lucien GENTIS -->
 <!-- Reviewed by : Vincent Deffontaines -->
 
-- 
2.40.0