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.

diff --git a/doc/configuration.txt b/doc/configuration.txt
index 7b3364f92ddc56c9d99b105e4a8c9dea0d7cff50..d46905bee82bfc52ff4a88a56d49a93dd9f6a9bd 100644 (file)
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -16952,11 +16952,11 @@ tfo
   "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