Mention compile-time directives and where they're documented.

[u/mdw/putty] / doc / config.but

diff --git a/doc/config.but b/doc/config.but
index e04120e..f1e03b4 100644 (file)
--- a/doc/config.but
+++ b/doc/config.but
@@ -538,7 +538,7 @@ help.
 (Typing \i{Shift-Backspace} will cause PuTTY to send whichever code
 isn't configured here as the default.)
 
-\S{config-homeend} Changing the action of the \I{Home and End keys}
+\S{config-homeend} Changing the action of the \i{Home and End keys}
 
 \cfg{winhelp-topic}{keyboard.homeend}
 
@@ -1590,7 +1590,7 @@ side doesn't believe there is an open connection any more.
 Keepalives can make this sort of problem worse, because they
 increase the probability that PuTTY will attempt to send data during
 a break in connectivity. (Other types of periodic network activity
-can cause this activity; in particular, SSH-2 re-keys can have
+can cause this behaviour; in particular, SSH-2 re-keys can have
 this effect. See \k{config-ssh-kex-rekey}.)
 
 Therefore, you might find that keepalives help
@@ -2393,6 +2393,11 @@ This key must be in PuTTY's native format (\c{*.\i{PPK}}). If you have a
 private key in another format that you want to use with PuTTY, see
 \k{puttygen-conversions}.
 
+If a key file is specified here, and \i{Pageant} is running (see
+\k{pageant}), PuTTY will first try asking Pageant to authenticate with
+that key, and ignore any other keys Pageant may have. If that fails,
+PuTTY will ask for a passphrase as normal.
+
 \H{config-ssh-tty} The TTY panel
 
 The TTY panel lets you configure the remote pseudo-terminal.