diff --git a/doc/gs.but b/doc/gs.but
index baf981f4..9a2dffbc 100644
--- a/doc/gs.but
+++ b/doc/gs.but
@@ -45,7 +45,17 @@ If you are not using the SSH
 If you are using SSH to connect to a server for the first time, you
 will probably see a message looking something like this:
 
-\# FIXME: copy the real message from the host key dialog
+\c The server's host key is not cached in the registry. You
+\c have no guarantee that the server is the computer you
+\c think it is.
+\c The server's key fingerprint is:
+\c ssh-rsa 1024 7b:e5:6f:a7:f4:f9:81:62:5c:e3:1f:bf:8b:57:6c:5a
+\c If you trust this host, hit Yes to add the key to
+\c PuTTY's cache and carry on connecting.
+\c If you want to carry on connecting just once, without
+\c adding the key to the cache, hit No.
+\c If you do not trust this host, hit Cancel to abandon the
+\c connection.
 
 This is a feature of the SSH protocol. It is designed to protect you
 against a network attack known as \e{spoofing}: secretly redirecting
diff --git a/doc/pageant.but b/doc/pageant.but
index 5e9411b4..28e378e5 100644
--- a/doc/pageant.but
+++ b/doc/pageant.but
@@ -4,8 +4,6 @@ Pageant is an SSH authentication agent. It holds your private keys
 in memory, already decoded, so that you can use them often without
 needing to type a passphrase.
 
-Currently, Pageant only works with SSH v1.
-
 \H{pageant-start} Getting started with Pageant
 
 Before you run Pageant, you need to have a private key. See
diff --git a/doc/plink.but b/doc/plink.but
index 8dfa0c04..b25faee9 100644
--- a/doc/plink.but
+++ b/doc/plink.but
@@ -1,4 +1,4 @@
-\versionid $Id: plink.but,v 1.7 2001/08/04 13:06:08 simon Exp $
+\versionid $Id: plink.but,v 1.8 2001/09/22 15:36:44 simon Exp $
 
 \C{plink} Using the command-line connection tool Plink
 
@@ -13,9 +13,9 @@
 
 \# Give instructions on how to set up Plink with CVS
 
-\i{Plink} (PuTTY Link), is a command-line connection tool similar to
-UNIX \c{ssh}.  It is probably not what you want if you want to run an
-interactive session in a console window.
+\i{Plink} (PuTTY Link) is a command-line connection tool similar to
+UNIX \c{ssh}.  It is probably not what you want if you want to run
+an interactive session in a console window.
 
 \H{plink-starting} Starting Plink
 
diff --git a/doc/pscp.but b/doc/pscp.but
index f31b8d5b..26bb8790 100644
--- a/doc/pscp.but
+++ b/doc/pscp.but
@@ -1,4 +1,4 @@
-\versionid $Id: pscp.but,v 1.13 2001/08/28 09:53:51 simon Exp $
+\versionid $Id: pscp.but,v 1.14 2001/09/22 15:36:44 simon Exp $
 
 \#FIXME: Need examples
 
@@ -267,4 +267,6 @@ For more general information on public-key authentication, see
 
 Lars Gunnarson has written a graphical interface for PSCP.  You can
 get it from his web site, at
-\W{http://www.i-tree.org/}{www.i-tree.org}.
+\W{http://members.surfeu.at/lgunnars/daplay/}{members.surfeu.at}.
+\# \W{http://www.i-tree.org/}{www.i-tree.org}.
+\# update this if the original site ever returns.
diff --git a/doc/pubkey.but b/doc/pubkey.but
index 871dfb81..6946fa96 100644
--- a/doc/pubkey.but
+++ b/doc/pubkey.but
@@ -1,4 +1,4 @@
-\versionid $Id: pubkey.but,v 1.3 2001/06/15 19:31:10 simon Exp $
+\versionid $Id: pubkey.but,v 1.4 2001/09/22 15:36:44 simon Exp $
 
 \# FIXME: passphrases, examples (e.g what does a key for pasting into
 \# authorized_keys look like?), index entries, links.
@@ -93,7 +93,7 @@ meaningful comment may help you remember which passphrase to use!  You
 should always enter a \e{Key passphrase} and \e{Confirm passphrase} to
 protect your keys.
 
-\# Mention a good length for a passphrase. (I think Schneier
+\# FIXME: Mention a good length for a passphrase. (I think Schneier
 \# said something about this on counterpane.com once.)
 
 \# In case people don't like the idea of exchanging a short password