Add input-focus support for System 7, where the Control Manager can't do

[u/mdw/putty] / doc / feedback.but

diff --git a/doc/feedback.but b/doc/feedback.but
index da329e5..9d14880 100644 (file)
--- a/doc/feedback.but
+++ b/doc/feedback.but
@@ -1,4 +1,4 @@
-\versionid $Id: feedback.but,v 1.10 2003/01/10 15:23:01 ben Exp $
+\versionid $Id: feedback.but,v 1.12 2003/01/24 14:12:31 jacob Exp $
 
 \A{feedback} Feedback and bug reporting
 
@@ -94,7 +94,7 @@ If you think you have found a bug in PuTTY, your first steps should
 be:
 
 \b Check the
-\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist.html}{Wishlist
+\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/}{Wishlist
 page} on the PuTTY website, and see if we already know about the
 problem. If we do, it is almost certainly not necessary to mail us
 about it, unless you think you have extra information that might be
@@ -189,7 +189,7 @@ If you want to request a new feature in PuTTY, the very first things
 you should do are:
 
 \b Check the
-\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist.html}{Wishlist
+\W{http://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/}{Wishlist
 page} on the PuTTY website, and see if your feature is already on
 the list. If it is, it probably won't achieve very much to repeat
 the request. (But see \k{feedback-feature-priority} if you want to
@@ -241,7 +241,8 @@ on the Wishlist, or we might think you haven't even \e{read} the
 Wishlist). This probably won't have very \e{much} effect; if a huge
 number of people vote for something then it may make a difference,
 but one or two extra votes for a particular feature are unlikely to
-change our priority list immediately. Also, don't expect a reply.
+change our priority list immediately. Offering a new and compelling
+justification might help. Also, don't expect a reply.
 
 \b Offer us money if we do the work sooner rather than later. This
 sometimes works, but not always. The PuTTY team all have full-time