diff --git a/tsshbatch.rst b/tsshbatch.rst
index 3f574c3..f548729 100644
--- a/tsshbatch.rst
+++ b/tsshbatch.rst
@@ -8,7 +8,7 @@
 SYNOPSIS
 --------
 
-tsshbatch.py [-Nehvk] [-n name] [-p pw] [-H 'h1 h2 ...' | hostlistfile] [command arg ... | -]
+tsshbatch.py [-Nehksv] [-n name] [-p pw] [-H 'h1 h2 ...' | hostlistfile] [command arg ... | -]
 
 
 DESCRIPTION
@@ -83,6 +83,8 @@
 
   -p pw          Password to use when logging in and/or doing sudo
 
+  -s             Force prompting for sudo password
+
   -v             Print detailed program version information and exit
 
 The last option on the command line is either an explicit command
@@ -313,20 +315,21 @@
 
    ``tsshbatch`` is smart enough to handle commands that begin with
    the ``sudo`` command.  It knows that such commands *require* a
-   password even if you used key exchange to initially log in.  That's
-   because, once you are logged in - whether via name/password or via
-   key exchange - ``sudo`` requires your password again to promote
-   your privileges.
+   password no matter how you initially authenticate to get into
+   the system.  If you provide a password - either via interactive
+   entry or the ``-p`` option - by default, ``tsshbatch`` will use
+   that same password for ``sudo`` promotion.  If you provide
+   no password - you're using ``-k`` and have not provided
+   a password via ``-p`` - ``tsshbatch`` will prompt you for
+   the password ``sudo`` should use.  You can force ``tsshbatch``
+   to ask you for a ``sudo`` password with the ``-s`` option.
+   This allows you to have one password for intiial login,
+   and a different one for ``sudo`` promotion.
 
-   When using name/password authentication, with ``tsshbatch`` you
-   need do nothing special to run ``sudo`` commands on your targeted
-   hosts (assuming you have the privilege of doing so there).
-
-   However, when using key exchange-based authentication, if you want
-   to run ``sudo`` commands, *you will also have to provide a
-   password* by one of the means described previously.  That's
-   because, once you are logged into a host, your password is required
-   again to do ``sudo`` privilege promotion.
+   Any time you a prompted for a ``sudo`` password and a
+   login password has been provided (interactive of ``-p``),
+   you can accept this as the ``sudo`` password by just
+   hitting ``Enter``.
 
 
 5) Precedence Of Authentication Options
@@ -405,10 +408,10 @@
 When ``sudo`` is presented a bad password, it ordinarily prints a
 string indicating something is wrong.  ``tsshbatch`` looks for this to
 let you know that you've got a problem and then terminates further
-operation.  This is so that you do not attempt to log in with a bad
-password across all the servers you have targeted.  (Many enterprises
-have policies to lock out a user ID after some small number of failed
-login/access attempts.)
+operation.  This is so that you do not attempt to log in
+with a bad password across all the servers you have targeted.  (Many
+enterprises have policies to lock out a user ID after some small
+number of failed login/access attempts.)
 
 However, some older versions of ``sudo`` (noted on a RHEL 4 server
 running ``sudo`` 1.6.7p5) do not return any feedback when presented
@@ -449,7 +452,7 @@
 
 ::
 
-  $Id: tsshbatch.rst,v 1.114 2013/10/22 19:30:49 tundra Exp $
+  $Id: tsshbatch.rst,v 1.115 2013/10/23 16:09:28 tundra Exp $
 
 You can find the latest version of this program at: