summaryrefslogtreecommitdiffstats
path: root/docs/manual
diff options
context:
space:
mode:
authorChristophe Jaillet <jailletc36@apache.org>2021-12-26 11:36:17 +0100
committerChristophe Jaillet <jailletc36@apache.org>2021-12-26 11:36:17 +0100
commit3f8a5522a9429326b550547f61b758c795c8b905 (patch)
tree4aff1f31675ca59fad1652895e80b6c8d1a29b4f /docs/manual
parentFix a typo and add a missing link to a directive (diff)
downloadapache2-3f8a5522a9429326b550547f61b758c795c8b905.tar.xz
apache2-3f8a5522a9429326b550547f61b758c795c8b905.zip
Fix a typo.
Prefer <code> to <var> when giving the value of a parameter Add a missing space Add a missing link [skip ci] git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1896413 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/manual')
-rw-r--r--docs/manual/mod/core.xml10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/manual/mod/core.xml b/docs/manual/mod/core.xml
index 2798615146..d637d9d896 100644
--- a/docs/manual/mod/core.xml
+++ b/docs/manual/mod/core.xml
@@ -2042,12 +2042,12 @@ to the network</description>
<usage>
<p>This directive allows to configure the maximum number of pipelined
responses, which remain pending so long as pipelined request are received.
- When the limit is reached, reponses are forcibly flushed to the network in
+ When the limit is reached, responses are forcibly flushed to the network in
blocking mode, until passing under the limit again.</p>
<p><directive>FlushMaxPipelined</directive> helps constraining memory
- usage. When set to <var>0</var> pipelining is disabled, when set to
- <var>-1</var> there is no limit (<directive>FlushMaxThreshold</directive>
+ usage. When set to <code>0</code> pipelining is disabled, when set to
+ <code>-1</code> there is no limit (<directive module="core">FlushMaxThreshold</directive>
still applies).</p>
</usage>
</directivesynopsis>
@@ -2056,7 +2056,7 @@ to the network</description>
<name>FlushMaxThreshold</name>
<description>Threshold above which pending data are flushed to the
network</description>
-<syntax>FlushMaxThreshold<var>number-of-bytes</var></syntax>
+<syntax>FlushMaxThreshold <var>number-of-bytes</var></syntax>
<default>FlushMaxThreshold 65536</default>
<contextlist><context>server config</context><context>virtual host</context>
</contextlist>
@@ -2068,7 +2068,7 @@ network</description>
the network in blocking mode, until passing under the limit again.</p>
<p><directive>FlushMaxThreshold</directive> helps constraining memory
- usage. When set to <var>0</var> or a too small value there are actually
+ usage. When set to <code>0</code> or a too small value there are actually
no pending data, but for threaded MPMs there can be more threads busy
waiting for the network thus less ones available to handle the other
simultaneous connections.</p>