DOC: config: use the word 'backend' instead of 'proxy' in 'track' description
User @nwehrman reported in issue #2328 that the used of "proxy" instead
of "backend" in the argument of the "track" server keyword is confusing.
Admittedly, all other places in the doc use "backend/server" instead of
"proxy/server", so let's update it for the sake of consistency.
(cherry picked from commit 9530e7dcd38f2a771558c75b40c7decf14c1bc7a)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>
diff --git a/doc/configuration.txt b/doc/configuration.txt
index 4de3c7e..56dc184 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -16746,11 +16746,11 @@
"empty-response" and "response-timeout" keywords for "retry-on", or HAProxy
won't be able to retry the connection on failure. See also "no-tfo".
-track [<proxy>/]<server>
+track [<backend>/]<server>
This option enables ability to set the current state of the server by tracking
another one. It is possible to track a server which itself tracks another
server, provided that at the end of the chain, a server has health checks
- enabled. If <proxy> is omitted the current one is used. If disable-on-404 is
+ enabled. If <backend> is omitted the current one is used. If disable-on-404 is
used, it has to be enabled on both proxies.
tls-tickets