I think the time has come for PuTTYgen to mention "authorized_keys" instead

[sgt/putty] / doc / feedback.but

diff --git a/doc/feedback.but b/doc/feedback.but
index 9d14880..a818cba 100644 (file)
--- a/doc/feedback.but
+++ b/doc/feedback.but
@@ -1,4 +1,4 @@
-\versionid $Id: feedback.but,v 1.12 2003/01/24 14:12:31 jacob Exp $
+\versionid $Id: feedback.but,v 1.15 2003/09/23 10:12:02 jacob Exp $
 
 \A{feedback} Feedback and bug reporting
 
@@ -133,6 +133,8 @@ delayed and it may not be obvious which version was the latest at
 the time you sent the message. 
 
 \b Tell us what version of what OS you are running PuTTY on.
+(If you're running on Windows for Alpha, tell us, or we'll assume
+you're running on Intel as this is overwhelmingly the case.)
 
 \b Tell us what protocol you are connecting with: SSH, Telnet,
 Rlogin or Raw mode.
@@ -195,7 +197,7 @@ 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
 persuade us to give your particular feature higher priority.)
 
-\b Check the
+\b Check the Wishlist and
 \W{http://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html}{Change
 Log} on the PuTTY website, and see if we have already added your
 feature in the development snapshots. If it isn't clear, download
@@ -281,6 +283,11 @@ a different SSH client and see if it works with that. Please do not
 report it as a PuTTY bug unless you are really sure it \e{is} a bug
 in PuTTY.
 
+\b If someone else installed PuTTY for you, or you're using PuTTY on
+someone else's computer, try asking them for help first.  They're more
+likely to understand how they installed it and what they expected you
+to use it for than we are.
+
 \b If you have successfully made a connection to your server and now
 need to know what to type at the server's command prompt, or other
 details of how to use the server-end software, talk to your server's