From: Tim Duesterhus <duesterhus@woltlab.com>
Date: Tue, 13 Jun 2023 13:15:47 +0000 (+0200)
Subject: DOC: Attempt to fix dconv parsing error for tune.h2.fe.initial-window-size
X-Git-Tag: v2.9-dev1~45
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=bd88998678997b30fe84858d76177ce558c090c6;p=thirdparty%2Fhaproxy.git

DOC: Attempt to fix dconv parsing error for tune.h2.fe.initial-window-size

It appears that dconv dislikes the "see also" part being on the same line as
the regular paragraph. The beginning of the line does not show up in the
rendered version.

Attempt to fix this by inserting an additional newline which is consistent with
other options.
---

diff --git a/doc/configuration.txt b/doc/configuration.txt
index 090d29928d..8bcfc3c064 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -2965,6 +2965,7 @@ tune.h2.be.initial-window-size <number>
   It can make sense to slightly increase this value to allow faster downloads
   or to reduce CPU usage on the servers, at the expense of creating unfairness
   between clients. It doesn't affect resource usage.
+
   See also: tune.h2.initial-window-size.
 
 tune.h2.be.max-concurrent-streams <number>
@@ -2991,7 +2992,9 @@ tune.h2.fe.initial-window-size <number>
   bandwidth per client over a 100 ms ping time, and 500 Mbps for 1 ms ping
   time. It doesn't affect resource usage. Using too large values may cause
   clients to experience a lack of responsiveness if pages are accessed in
-  parallel to large uploads. See also: tune.h2.initial-window-size.
+  parallel to large uploads.
+
+  See also: tune.h2.initial-window-size.
 
 tune.h2.fe.max-concurrent-streams <number>
   Sets the HTTP/2 maximum number of concurrent streams per incoming connection