X-Git-Url: https://asedeno.scripts.mit.edu/gitweb/?a=blobdiff_plain;f=doc%2Fpscp.but;h=78a5afb98b9fa4e2e2b94574ef9521cf954f7216;hb=d77102a8d535a7000d6d909529a61a1564f6d678;hp=e5f1778ceadf216f381140e8a5f99337976b85f4;hpb=5d32d4af14c880458971e848886fa6f315b5c5a1;p=PuTTY.git

diff --git a/doc/pscp.but b/doc/pscp.but
index e5f1778c..78a5afb9 100644
--- a/doc/pscp.but
+++ b/doc/pscp.but
@@ -241,9 +241,10 @@ security issue described in \k{pscp-usage-basics}.
 
 The newer SFTP protocol, which is usually associated with SSH 2
 servers, is specified in a more platform independent way, and leaves
-issues such as wildcard syntax up to the client. This makes it more
-consistent across platforms, more suitable for scripting and
-automation, and avoids security issues with wilcard matching.
+issues such as wildcard syntax up to the client. (PuTTY's SFTP
+wildcard syntax is described in \k{psftp-wildcards}.) This makes it
+more consistent across platforms, more suitable for scripting and
+automation, and avoids security issues with wildcard matching.
 
 Normally PSCP will attempt to use the SFTP protocol, and only fall
 back to the SCP protocol if SFTP is not available on the server.