Oops - that tweak had bad Buttress syntax. D'oh!

[sgt/putty] / doc / plink.but

diff --git a/doc/plink.but b/doc/plink.but
index cdee880..b25faee 100644 (file)
--- a/doc/plink.but
+++ b/doc/plink.but
@@ -1,4 +1,4 @@
-\versionid $Id: plink.but,v 1.5 2001/04/18 15:23:36 owen Exp $
+\versionid $Id: plink.but,v 1.8 2001/09/22 15:36:44 simon Exp $
 
 \C{plink} Using the command-line connection tool Plink
 
@@ -13,9 +13,9 @@
 
 \# Give instructions on how to set up Plink with CVS
 
-\i{Plink} (PuTTY Link), is a command-line connection tool similar to
-UNIX \c{ssh}.  It is probably not what you want if you want to run an
-interactive session in a console window.
+\i{Plink} (PuTTY Link) is a command-line connection tool similar to
+UNIX \c{ssh}.  It is probably not what you want if you want to run
+an interactive session in a console window.
 
 \H{plink-starting} Starting Plink
 
@@ -30,7 +30,7 @@ To start Plink it will need either to be on your \i{\c{PATH}} or in your
 current directory.  To add the directory containing Plink to your
 \c{PATH} environment variable, type into the console window:
 
-\c set PATH C:\path\to\putty\directory;%PATH%
+\c set PATH=C:\path\to\putty\directory;%PATH%
 
 This will only work for the lifetime of that particular console
 window.  To set your \c{PATH} more permanently on Windows NT, use the
@@ -120,6 +120,10 @@ Alternatively, you can use Pageant if Pageant is running (see
 
 \b Ensure Pageant is running, and has your private key stored in it.
 
+\b Set the environment variable \cw{PLINK_PROTOCOL} to the string
+\c{ssh}, to make sure Plink will try to connect using SSH instead of
+Telnet.
+
 \b Run CVS as follows:
 
 \c cvs -d :ext:user@hostname:/path/to/repository co module