X-Git-Url: https://git.distorted.org.uk/u/mdw/putty/blobdiff_plain/b41cfbb576b48edac06c0ca077aa926ba7042ef6..479fb46358969757f85b387630ae54b6fa8d8a36:/doc/pubkey.but

diff --git a/doc/pubkey.but b/doc/pubkey.but
index f1223a4f..ee4b600b 100644
--- a/doc/pubkey.but
+++ b/doc/pubkey.but
@@ -243,7 +243,7 @@ If you leave the passphrase fields blank, the key will be saved
 unencrypted. You should \e{not} do this without good reason; if you
 do, your private key file on disk will be all an attacker needs to
 gain access to any machine configured to accept that key. If you
-want to be able to \i{passwordless login}log in without having to
+want to be able to \I{passwordless login}log in without having to
 type a passphrase every time, you should consider using Pageant
 (\k{pageant}) so that your decrypted key is only held in memory
 rather than on disk.
@@ -291,8 +291,8 @@ will need to tell PuTTY to use for authentication (see
 
 \cfg{winhelp-topic}{puttygen.savepub}
 
-The SSH-2 protocol drafts specify a \I{SSH-2 public key format}standard
-format for storing public keys on disk. Some SSH servers (such as
+RFC 4716 specifies a \I{SSH-2 public key format}standard format for
+storing SSH-2 public keys on disk. Some SSH servers (such as
 \i\cw{ssh.com}'s) require a public key in this format in order to accept
 authentication with the corresponding private key. (Others, such as
 OpenSSH, use a different format; see \k{puttygen-pastekey}.)