mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-01-20 17:41:06 +01:00
DOC: fix mismatched quotes typos around words in the documentation files
s/"no'/"no" s/'private"/"private" s/"flt'/"flt" There isn't definite convention but people usually prefer to highlight something important with quotation marks. For example, it's convenient to find keywords from a text when they are quoted, mismatches make this harder. No backport needed.
This commit is contained in:
parent
0c3b212aab
commit
44c491ae6b
@ -2753,7 +2753,7 @@ h2-workaround-bogus-websocket-clients
|
||||
automatically downgrade to http/1.1 for the websocket tunnel, specify h2
|
||||
support on the bind line using "alpn" without an explicit "proto" keyword. If
|
||||
this statement was previously activated, this can be disabled by prefixing
|
||||
the keyword with "no'.
|
||||
the keyword with "no".
|
||||
|
||||
hard-stop-after <time>
|
||||
Defines the maximum time allowed to perform a clean soft-stop.
|
||||
@ -19353,7 +19353,7 @@ strict-maxconn
|
||||
then never establish more connections to a server than maxconn, and try to
|
||||
reuse or kill connections if needed. Please note, however, than it may lead
|
||||
to failed requests in case we can't establish a new connection, and no
|
||||
idle connection is available. This can happen when 'private" connections
|
||||
idle connection is available. This can happen when "private" connections
|
||||
are established, connections tied only to a session, because authentication
|
||||
happened.
|
||||
|
||||
|
||||
@ -3627,7 +3627,7 @@ show stat [domain <resolvers|proxy>] [{<iid>|<proxy>} <type> <sid>] \
|
||||
format" described in the section above. In short, the second column (after the
|
||||
first ':') indicates the origin, nature, scope and persistence state of the
|
||||
variable. The third column indicates the field type, among "s32", "s64",
|
||||
"u32", "u64", "flt' and "str". Then the fourth column is the value itself,
|
||||
"u32", "u64", "flt" and "str". Then the fourth column is the value itself,
|
||||
which the consumer knows how to parse thanks to column 3 and how to process
|
||||
thanks to column 2.
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user