Fix a broken gitweb link.

[PuTTY.git] / doc / faq.but

diff --git a/doc/faq.but b/doc/faq.but
index 2ad5f18096dceeb8faf4239503461d39a84c11c8..03de70d780ebfd657c4cfb87145a7858f0e00f1b 100644 (file)
--- a/doc/faq.but
+++ b/doc/faq.but
@@ -167,7 +167,7 @@ the wrong solution and we will not do it.
 
 If you have host keys available in the common \i\c{known_hosts} format,
 we have a script called 
-\W{http://tartarus.org/~simon-git/gitweb/?p=putty.git;a=blob;f=contrib/kh2reg.py;hb=HEAD}\c{kh2reg.py}
+\W{https://git.tartarus.org/?p=simon/putty.git;a=blob;f=contrib/kh2reg.py;hb=HEAD}\c{kh2reg.py}
 to convert them to a Windows .REG file, which can be installed ahead of
 time by double-clicking or using \c{REGEDIT}.
 
@@ -216,12 +216,13 @@ 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.
-\#{XXX-REVIEW-BEFORE-RELEASE: should say something about w32old for
-pre-XP Windows}
+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.
 
 The 32-bit Windows executables we provide for the \q{\i{x86}}
 processor architecture should also work fine on 64-bit processors
@@ -1092,15 +1093,21 @@ USB stick).
 I \i{clean up} after it?
 
 PuTTY will leave some Registry entries, and a random seed file, on
-the PC (see \k{faq-settings}). If you are using PuTTY on a public
-PC, or somebody else's PC, you might want to clean these up when you
-leave. You can do that automatically, by running the command
-\c{putty -cleanup}. (Note that this only removes settings for
-the currently logged-in user on \i{multi-user systems}.)
+the PC (see \k{faq-settings}). Windows 7 and up also remember some
+information about recently launched sessions for the \q{jump list}
+feature.
+
+If you are using PuTTY on a public PC, or somebody else's PC, you
+might want to clean this information up when you leave. You can do
+that automatically, by running the command \c{putty -cleanup}. See
+\k{using-cleanup} in the documentation for more detail. (Note that
+this only removes settings for the currently logged-in user on
+\i{multi-user systems}.)
 
 If PuTTY was installed from the installer package, it will also
-appear in \q{Add/Remove Programs}. Older versions of the uninstaller
-do not remove the above-mentioned registry entries and file.
+appear in \q{Add/Remove Programs}. Current versions of the installer
+do not offer to remove the above-mentioned items, so if you want them
+removed you should run \c{putty -cleanup} before uninstalling.
 
 \S{faq-dsa}{Question} How come PuTTY now supports \i{DSA}, when the
 website used to say how insecure it was?