diff --git a/tsshbatch.rst b/tsshbatch.rst
index dfaa9a1..bdd706c 100644
--- a/tsshbatch.rst
+++ b/tsshbatch.rst
@@ -93,10 +93,10 @@
          curly.foo.com
          moe.foo.com
 
-       This method is handy when there are standard "sets" of hosts
-       on which you regularly work.  For instance, you may wish to
-       keep a host file lis for each of your production hosts, each
-       of your test hosts, each of your AIX hosts, and so on.
+       This method is handy when there are standard "sets" of hosts on
+       which you regularly work.  For instance, you may wish to keep a
+       host file list for each of your production hosts, each of your
+       test hosts, each of your AIX hosts, and so on.
 
 
 2) Authentication Using Name And Password
@@ -106,11 +106,10 @@
 
      tsshbatch.py linux-prod-hosts uptime
 
-   You will be promted for your username and password one time
-   which ``tsshbatch`` will then use to log into each of the
-   machines named in ``linux-prod-hosts``.  (*Notice that
-   his assumes your name and password are the same on each
-   host!*)
+   You will be prompted for your username and password one time which
+   ``tsshbatch`` will then use to log into each of the machines named
+   in ``linux-prod-hosts``.  (*Notice that his assumes your name and
+   password are the same on each host!*)
 
    Typing in your login credentials all the time can get tedious after
    awhile so ``tsshbatch`` provides a means of providing them on the
@@ -208,8 +207,8 @@
    key-based authentication.  For this to work, you must first have
    pushed ssh keys to all your hosts.  You then instruct ``tsshbatch``
    to use key-based authentication rather than name and password.  Not
-   only does this elimintate the need to constantly provide name and
-   passowrd, it also eliminates passing a plain text password on the
+   only does this eliminate the need to constantly provide name and
+   password, it also eliminates passing a plain text password on the
    command line and is thus far more secure.  This also overcomes the
    problem of having different name/password credentials on different
    hosts.
@@ -225,7 +224,7 @@
 
    ``tsshbatch`` is smart enough to handle commands that begin
    with ``sudo``.  It knows that such commands *require* a password
-   even if you used key exchange to intially log in.  That's because,
+   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.
@@ -245,6 +244,16 @@
 OTHER
 -----
 
+``tsshbatch`` writes the ``stdout`` of the remote host(s) to
+``stdout`` on the local machine.  It similarly writes remote
+``stderr`` output to the local machine's ``stderr``.  If you wish to
+suppress ``stderr`` output, either redirect it on your local command
+line or use the ``-e`` option to turn it off entirely.
+
+You will not be able to run remote ``sudo`` commands if the host
+in question enables the ``Defaults requiretty`` in its ``sudoers``
+configuration.
+
 You must have a reasonably current version of Python installed.  If
 your Python installation does not install ``paramiko`` you'll have to
 install it manually, since ``tsshbatch`` requires these libraries.
@@ -300,7 +309,7 @@
 
 ::
 
-  $Id: tsshbatch.rst,v 1.108 2012/01/05 19:09:11 tundra Exp $
+  $Id: tsshbatch.rst,v 1.109 2012/01/17 14:58:52 tundra Exp $
 
 You can find the latest version of this program at: