DOC: fix a few reported typos in the config and install doc

These are only the few relevant changes among those reported here:

  https://github.com/haproxy/haproxy/actions/runs/4856148287/jobs/8655397661

diff --git a/INSTALL b/INSTALL
index 400513d0a38bb6ad9514d634bd168b74849c4988..81f7175d7f2de9dcd2ec86c4b34349eeb1a28e9a 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -482,7 +482,7 @@ and see what is happening. However it is not convenient at all to observe what
 flags are passed to the compiler nor what compiler is involved. Simply append
 "V=1" to the "make" command line to switch to verbose mode and display the
 details again. It is recommended to use this option when cross-compiling to
-verify that the paths are correct and that /usr/include is never invovled.
+verify that the paths are correct and that /usr/include is never involved.
 
 You may want to build specific target binaries which do not match your native
 compiler's target. This is particularly true on 64-bit systems when you want

diff --git a/doc/configuration.txt b/doc/configuration.txt
index 1998dab6c995e2f97b10df2d25826f8466cc9cf4..5cfda4e4e3dad7c14b3faa1b613565ecd44af108 100644 (file)
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -2986,7 +2986,7 @@ tune.h2.initial-window-size <number>
 
 tune.h2.max-concurrent-streams <number>
   Sets the default HTTP/2 maximum number of concurrent streams per connection
-  (i.e. the number of outstanding requests on a single connection). Ths value
+  (i.e. the number of outstanding requests on a single connection). This value
   is used for incoming connections when tune.h2.fe.max-concurrent-streams is
   not set, and for outgoing connections when tune.h2.be.max-concurrent-streams
   is not set. The default value is 100. The impact varies depending on the side
@@ -3097,7 +3097,7 @@ tune.listener.multi-queue { on | fair | off }
   the probability to find the least loaded thread with the first mode is low.
   Finally it is possible to forcefully disable the redistribution mechanism
   using "off" for troubleshooting, or for situations where connections are
-  short-lived and it is estimated that the operating system alredy provides a
+  short-lived and it is estimated that the operating system already provides a
   good enough distribution. The default is "on".
 
 tune.lua.forced-yield <number>