From: Luca Toscano <elukey@apache.org>
Date: Sun, 11 Feb 2018 11:11:31 +0000 (+0000)
Subject: documentation rebuild
X-Git-Tag: 2.4.30~81
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2b02176ee46fb6c0d28c4200172aa1735ebe9af7;p=thirdparty%2Fapache%2Fhttpd.git

documentation rebuild

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

diff --git a/docs/manual/mod/mod_proxy_fcgi.html.en b/docs/manual/mod/mod_proxy_fcgi.html.en
index 4d2f56511fe..082874ace58 100644
--- a/docs/manual/mod/mod_proxy_fcgi.html.en
+++ b/docs/manual/mod/mod_proxy_fcgi.html.en
@@ -99,8 +99,9 @@
     By default mod_proxy (configured with <code>enablereuse=on</code>)
     allows a connection pool of
     <code class="directive"><a href="../mod/mpm_common.html#threadsperchild">ThreadsPerChild</a></code> connections to the
-    backend for each httpd process, so the following use cases should be taken
-    into account:</p>
+    backend for each httpd process when using a threaded mpm (like
+    <code class="module"><a href="../mod/worker.html">worker</a></code> or <code class="module"><a href="../mod/event.html">event</a></code>),
+    so the following use cases should be taken into account:</p>
     <ul>
       <li>Under HTTP/1.1 load it will likely cause the creation of up to
       <code class="directive"><a href="../mod/mpm_common.html#maxrequestworkers">MaxRequestWorkers</a></code>