X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=doc%2Fconfig.but;h=cb7eb6670146509c31b00a9e9de65787cca5e5a3;hb=3f8bd285983e7cbf677d2469990a72e1dd94be16;hp=646b5712c6c6a1b49dc206ce024715a2b8c2d88b;hpb=726f9dde7e747f0e317da6fbe0594a81597d4a2b;p=PuTTY.git

diff --git a/doc/config.but b/doc/config.but
index 646b5712..cb7eb667 100644
--- a/doc/config.but
+++ b/doc/config.but
@@ -1,4 +1,4 @@
-\versionid $Id: config.but,v 1.23 2001/12/29 17:21:26 simon Exp $
+\versionid $Id: config.but,v 1.25 2002/02/04 13:18:54 simon Exp $
 
 \C{config} Configuring PuTTY
 
@@ -330,6 +330,11 @@ multiple times at the keyboard. If you set the answerback string to
 be empty, this problem should go away, but doing so might cause
 other problems.
 
+Note that this is \e{not} the feature of PuTTY which the server will
+typically use to determine your terminal type. That feature is the
+\q{Terminal-type string} in the Connection panel; see
+\k{config-termtype} for details.
+
 \S{config-localecho} \q{Local echo}
 
 \cfg{winhelp-topic}{terminal.localecho}
@@ -1293,12 +1298,12 @@ the Telnet special backspace code, and Control-C will send the
 Telnet special interrupt code. You probably shouldn't enable this
 unless you know what you're doing.
 
-\S{config-telnetkey} \q{Return key sends telnet New Line instead of ^M}
+\S{config-telnetnl} \q{Return key sends telnet New Line instead of ^M}
 
 \cfg{winhelp-topic}{telnet.newline}
 
 Unlike most other remote login protocols, the Telnet protocol has a
-special \Q{new line} code that is not the same as the usual line
+special \q{new line} code that is not the same as the usual line
 endings of Control-M or Control-J. By default, PuTTY sends the
 Telnet New Line code when you press Return, instead of sending
 Control-M as it does in most other protocols.