diff --git a/tsshbatch.rst b/tsshbatch.rst
index f548729..b4554fb 100644
--- a/tsshbatch.rst
+++ b/tsshbatch.rst
@@ -8,7 +8,7 @@
 SYNOPSIS
 --------
 
-tsshbatch.py [-Nehksv] [-n name] [-p pw] [-H 'h1 h2 ...' | hostlistfile] [command arg ... | -]
+tsshbatch.py [-NSehksv] [-n name] [-p pw] [-H 'h1 h2 ...' | hostlistfile] [command arg ... | -]
 
 
 DESCRIPTION
@@ -73,6 +73,8 @@
                  This copies ``/foo/bar/baz`` on the local
                  machine to ``/tmp/`` on every host in  ``hostlist``.
 
+  -S             Force prompting for sudo password
+
   -e             Don't report remote host stderr output
 
   -h             Print help information
@@ -83,12 +85,10 @@
 
   -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
-string or the ``-``.  If you provide an explicit command,
+string or the ``-`` character.  If you provide an explicit command,
 ``tsshbatch`` will attempt to execute it on every host you've
 specified either via ``-H`` or a ``hostlistfile``::
 
@@ -315,21 +315,22 @@
 
    ``tsshbatch`` is smart enough to handle commands that begin with
    the ``sudo`` command.  It knows that such commands *require* a
-   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.
+   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.  
 
-   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``.
+   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
+   intitial login, and a different one for ``sudo`` 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
@@ -338,10 +339,10 @@
    in a particular heirarchy using a "first match wins"
    scheme.   From highest to lowest, the precedence is:
 
-       1. Key Exchange
-       2. ``-n`` and ``-p`` options on command line or in ``$TSSHBATCH``
-       3. Forced interactive prompting for user name with ``$USER`` as the default.
-       4. Using ``$USER`` as the login name and prompting only for password. (Default program behavior).
+      1. Key exchange
+      2. Forced prompting for name via -N
+      3. Command Line/$TSSHBATCH env variable sets name
+      4. Name picked up from $USER  (Default behavior)
 
    If try to use Key Exchange and ``tsshbatch`` detects a command
    beginning with ``sudo``, it will prompt you for a password anyway.
@@ -452,7 +453,7 @@
 
 ::
 
-  $Id: tsshbatch.rst,v 1.115 2013/10/23 16:09:28 tundra Exp $
+  $Id: tsshbatch.rst,v 1.116 2013/10/23 18:10:17 tundra Exp $
 
 You can find the latest version of this program at: