connect-to.d: clarified

1 files changed, 12 insertions, 9 deletions

diff --git a/docs/cmdline-opts/connect-to.d b/docs/cmdline-opts/connect-to.d
index 3fa0568a6..20fbb70cc 100644
--- a/docs/cmdline-opts/connect-to.d
+++ b/docs/cmdline-opts/connect-to.d
@@ -5,14 +5,17 @@ Added: 7.49.0
 See-also: resolve header
 ---
 
-For a request to the given HOST:PORT pair, connect to
-CONNECT-TO-HOST:CONNECT-TO-PORT instead.  This option is suitable to direct
-requests at a specific server, e.g. at a specific cluster node in a cluster of
-servers.  This option is only used to establish the network connection. It
-does NOT affect the hostname/port that is used for TLS/SSL (e.g. SNI,
-certificate verification) or for the application protocols.  "host" and "port"
-may be the empty string, meaning "any host/port".  "connect-to-host" and
-"connect-to-port" may also be the empty string, meaning "use the request's
-original host/port".
+For a request to the given HOST1:PORT1 pair, connect to HOST2:PORT2 instead.
+This option is suitable to direct requests at a specific server, e.g. at a
+specific cluster node in a cluster of servers. This option is only used to
+establish the network connection. It does NOT affect the hostname/port that is
+used for TLS/SSL (e.g. SNI, certificate verification) or for the application
+protocols. "HOST1" and "PORT1" may be the empty string, meaning "any
+host/port". "HOST2" and "PORT2" may also be the empty string, meaning "use the
+request's original host/port".
+
+The "hosts" specified to this optionare compared as strings, so it need to
+match the string used in the request URL but can be either numerical such as
+"127.0.0.1" or the full host name such as "example.org".
 
 This option can be used many times to add many connect rules.