Clear out more XXX-REVIEW-BEFORE-RELEASE.

[PuTTY.git] / doc / faq.but

diff --git a/doc/faq.but b/doc/faq.but
index 03de70d780ebfd657c4cfb87145a7858f0e00f1b..ba0d53213f3568011122e39cf192c8c615252800 100644 (file)
--- a/doc/faq.but
+++ b/doc/faq.but
@@ -66,9 +66,8 @@ Yes. SSH-1 support has always been available in PuTTY.
 However, the SSH-1 protocol has many weaknesses and is no longer
 considered secure; you should use SSH-2 instead if at all possible.
 
-\#{XXX-REVIEW-BEFORE-RELEASE:
 As of 0.68, PuTTY will no longer fall back to SSH-1 if the server
-doesn't appear to support SSH-2; you must explicitly ask for SSH-1. }
+doesn't appear to support SSH-2; you must explicitly ask for SSH-1.
 
 \S{faq-localecho}{Question} Does PuTTY support \i{local echo}?
 
@@ -216,21 +215,17 @@ seems to be working so far.
 Currently, release versions of PuTTY tools only run on Windows
 systems and Unix.
 
-\#{XXX-REVIEW-BEFORE-RELEASE: replace following two lines with:
 As of 0.68, the supplied PuTTY executables run on versions of
-Windows from XP onwards,}
-PuTTY runs on versions of Windows from Windows 95 onwards (but not
-the 16-bit Windows 3.1; see \k{faq-win31}),
-up to and including Windows 10; and we know of no reason why PuTTY
-should not continue to work on future versions of Windows.
+Windows from XP onwards, up to and including Windows 10; and we
+know of no reason why PuTTY should not continue to work on
+future versions of Windows.
 
 The 32-bit Windows executables we provide for the \q{\i{x86}}
 processor architecture should also work fine on 64-bit processors
-that are backward-compatible with that architecture.
-\#{XXX-REVIEW-BEFORE-RELEASE: The 64-bit executables will only
-work on 64-bit versions of Windows. They will run somewhat faster
-than 32-bit executables would on the same processor, but will
-consume slightly more memory.}
+that are backward-compatible with that architecture. The 64-bit
+executables will only work on 64-bit versions of Windows. They
+will run somewhat faster than 32-bit executables would on the
+same processor, but will consume slightly more memory.
 
 (We used to also provide executables for Windows for the Alpha
 processor, but stopped after 0.58 due to lack of interest.)
@@ -257,10 +252,9 @@ If you look at the source release, you should find a \c{unix}
 subdirectory. There are a couple of ways of building it,
 including the usual \c{configure}/\c{make}; see the file \c{README}
 in the source distribution. This should build you Unix
-ports of Plink, PuTTY itself, PuTTYgen, PSCP, PSFTP, and also
+ports of Plink, PuTTY itself, PuTTYgen, PSCP, PSFTP, Pageant, and also
 \i\c{pterm} - an \cw{xterm}-type program which supports the same
-terminal emulation as PuTTY. \#{XXX-REVIEW-BEFORE-RELEASE:}
-We do not yet have a Unix port of Pageant.
+terminal emulation as PuTTY.
 
 If you don't have \i{Gtk}, you should still be able to build the
 command-line tools.
@@ -1054,8 +1048,7 @@ is triggered by PuTTY 0.58. This was fixed in 0.59. The
 \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/xp-wont-run}{\q{xp-wont-run}}
 entry in PuTTY's wishlist has more details.
 
-\S{faq-system32}{Question} When I put
-\#{XXX-REVIEW-BEFORE-RELEASE 32-bit} PuTTY in
+\S{faq-system32}{Question} When I put 32-bit PuTTY in
 \cw{C:\\WINDOWS\\\i{SYSTEM32}} on my \i{64-bit Windows} system,
 \i{\q{Duplicate Session}} doesn't work.