X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=doc%2Fpgpkeys.but;h=cdb0e93826e5d1b8978ad2834b9539037c3f4239;hb=a580c22c2419a9236466ca8ee80bc97bc9da41eb;hp=79768c35f2f1f0dc1a0e5725db8b94deb2549d59;hpb=0e82598a3589b15a9f4db1bc8a3357f28922441c;p=PuTTY.git

diff --git a/doc/pgpkeys.but b/doc/pgpkeys.but
index 79768c35..cdb0e938 100644
--- a/doc/pgpkeys.but
+++ b/doc/pgpkeys.but
@@ -12,13 +12,11 @@ accurate idea of what each signature guarantees.
 This description is provided as both a web page on the PuTTY site, and
 an appendix in the PuTTY manual.
 
-As of the next release, all of the PuTTY executables will contain
-\#{XXX-REMOVE-BEFORE-RELEASE: fix this up for forthcoming release
-As of release 0.58, all of the PuTTY executables contain}
-fingerprint material (usually accessed via the \i\c{-pgpfp}
-command-line option), such that if you have an executable you trust,
-you can use it to establish a trust path, for instance to a newer
-version downloaded from the Internet.
+As of release 0.58, all of the PuTTY executables contain fingerprint
+material (usually accessed via the \i\c{-pgpfp} command-line
+option), such that if you have an executable you trust, you can use
+it to establish a trust path, for instance to a newer version
+downloaded from the Internet.
 
 (Note that none of the keys, signatures, etc mentioned here have
 anything to do with keys used with SSH - they are purely for verifying