diff --git a/tperimeter.txt b/tperimeter.txt
index a1fe264..e483dc9 100644
--- a/tperimeter.txt
+++ b/tperimeter.txt
@@ -1,4 +1,4 @@
-.. footer:: $Id: tperimeter.txt,v 1.111 2006/09/25 18:50:18 tundra Exp $
+.. footer:: $Id: tperimeter.txt,v 1.112 2006/09/25 18:56:13 tundra Exp $
 
 
 =====================================================
@@ -65,7 +65,7 @@
 
   3) The ``cron`` job then *deletes* the request from the
      ``tperimeter`` queue.  This means that the next time
-     ``hosts.allow`` is rebuilt by the ``cron``job, the "hole"
+     ``hosts.allow`` is rebuilt by the ``cron`` job, the "hole"
      ``tperimeter`` opened in the tcp wrappers will be *removed*.
      This ensures that someone doesn't open a hole in the system that
      then stays there permanently.  This works fine in practice,
@@ -86,9 +86,9 @@
 subsequent processing.
 
 ``rebuild-hosts.allow.sh`` is the tcp wrapper rewrite mechanism.
-It is intended to be run periodically as a root ``cron``job.  Remember
+It is intended to be run periodically as a root ``cron`` job.  Remember
 that the "hole" ``tperimeter`` opens in your wrappers stays in
-place until the *next time* the ``cron``job runs.  We thus recommend
+place until the *next time* the ``cron`` job runs.  We thus recommend
 running this script every 5 to 10 minutes to keep the window of
 exposure small.
 
@@ -183,7 +183,7 @@
 "standard" tcp wrapper file - i.e., The ``hosts.allow`` entries you
 *always* want in place regardless whether or not there is pending
 requests for temporary access via the web interface.  That's because
-``rebuild-hosts.allow.sh`` runs periodically under ``cron``control and
+``rebuild-hosts.allow.sh`` runs periodically under ``cron`` control and
 rebuilds the *entire* ``hosts.allow`` file.  
 
 To make this simple, the list of things you always want in your