DOC: fix a few remainig cases of "Haproxy" and "HAproxy" in doc and comments
Some of the Lua doc and a few places still used "Haproxy" or "HAproxy".
There was even one "HA proxy". A few of them were in an example of VTest
output, indicating that VTest ought to be fixed as well. No big deal but
better address all the remaining ones so that these inconsistencies stop
spreading around.
diff --git a/doc/internals/hashing.txt b/doc/internals/hashing.txt
index da358b0..1541b61 100644
--- a/doc/internals/hashing.txt
+++ b/doc/internals/hashing.txt
@@ -1,6 +1,6 @@
2013/11/20 - How hashing works internally in haproxy - maddalab@gmail.com
-This document describes how Haproxy implements hashing both map-based and
+This document describes how HAProxy implements hashing both map-based and
consistent hashing, both prior to versions 1.5 and the motivation and tests
that were done when providing additional options starting in version 2.2
@@ -28,7 +28,7 @@
a randomly picked number falls equally before any server position, which is
ideal for consistently hashed backends, a common use case for caches.
-In all versions 1.4 and prior Haproxy implements the SDBM hashing function.
+In all versions 1.4 and prior HAProxy implements the SDBM hashing function.
However tests show that alternatives to SDBM have a better cache
distribution on different hashing criteria. Additional tests involving
alternatives for hash input and an option to trigger avalanche, we found
diff --git a/doc/internals/htx-api.txt b/doc/internals/htx-api.txt
index 516cd67..971328b 100644
--- a/doc/internals/htx-api.txt
+++ b/doc/internals/htx-api.txt
@@ -299,7 +299,7 @@
Both functions return a "zero-sized" HTX message if the buffer is null. This
way, the HTX message is always valid. The first function is the default function
to use. The second one is only useful when some content will be added. For
-instance, it used by the HTX analyzers when HAproxy generates a response. Thus,
+instance, it used by the HTX analyzers when HAProxy generates a response. Thus,
the buffer is in a right state.
Once the processing done, if the HTX message has been modified, the underlying