Bleh, grammar.

[PuTTY.git] / doc / config.but

diff --git a/doc/config.but b/doc/config.but
index 2279db58aa348a9d6df4db853fe695bf9ded985b..063d2a13412b887177ac4d8b82be3a42c20ee20d 100644 (file)
--- a/doc/config.but
+++ b/doc/config.but
@@ -1,4 +1,4 @@
-\versionid $Id: config.but,v 1.84 2004/06/20 17:07:36 jacob Exp $
+\versionid $Id: config.but,v 1.88 2004/09/01 10:19:22 jacob Exp $
 
 \C{config} Configuring PuTTY
 
@@ -1447,8 +1447,9 @@ badly to the default value.
 
 The format is a pair of numbers separated by a comma, for instance,
 \c{38400,38400}. The first number represents the output speed
-(\e{from} the server), and the second is the input speed (\e{to} the
-server). (Only the first is used in the Rlogin protocol.)
+(\e{from} the server) in bits per second, and the second is the input
+speed (\e{to} the server). (Only the first is used in the Rlogin
+protocol.)
 
 This option has no effect on Raw connections.
 
@@ -1549,7 +1550,7 @@ be configured within PuTTY.
 it may send out more in quick succession and if terminate the connection
 if no response is received.
 
-TCP keepalives may be useful for ensuring that half-open connections
+TCP keepalives may be more useful for ensuring that half-open connections
 are terminated than for keeping a connection alive.
 
 TCP keepalives are disabled by default.
@@ -1674,6 +1675,18 @@ Authentication is not fully supported for all forms of proxy:
 \b Username and password authentication is supported for HTTP
 proxies and SOCKS 5 proxies.
 
+\lcont{
+
+\b With SOCKS 5, authentication is via \i{CHAP} if the proxy
+supports it (this is not supported in \i{PuTTYtel}); otherwise the
+password is sent to the proxy in plain text.
+
+\b With HTTP proxying, the only currently supported authentication
+method is \q{basic}, where the password is sent to the proxy in plain
+text.
+
+}
+
 \b SOCKS 4 can use the \q{Username} field, but does not support
 passwords.