diff --git a/manpages/shorewall-tcdevices.xml b/manpages/shorewall-tcdevices.xml
index 2d79ebd43..e5045cf19 100644
--- a/manpages/shorewall-tcdevices.xml
+++ b/manpages/shorewall-tcdevices.xml
@@ -24,8 +24,8 @@
     <para>Entries in this file define the bandwidth for interfaces on which
     you want traffic shaping to be enabled.</para>
 
-    <para> If you do not plan to use traffic shaping for a device, don't put
-    it in here as it limits the troughput of that device to the limits you set
+    <para>If you do not plan to use traffic shaping for a device, don't put it
+    in here as it limits the troughput of that device to the limits you set
     here.</para>
 
     <para>The columns in the file are as follows.</para>
@@ -39,7 +39,7 @@
           this file. You may NOT specify the name of an alias (e.g., eth0:0)
           here; see http://www.shorewall.net/FAQ.htm#faq18</para>
 
-          <para>You man NOT specify wildcards here, e.g. if you have multiple
+          <para>You may NOT specify wildcards here, e.g. if you have multiple
           ppp interfaces, you need to put them all in here!</para>
 
           <para>If the device doesn't exist, a warning message will be issued
@@ -74,12 +74,12 @@
 
         <listitem>
           <para>The outgoing Bandwidth of that interface. This is the maximum
-          speed you connection can handle. It is also the speed you can refer
+          speed your connection can handle. It is also the speed you can refer
           as "full" if you define the tc classes. Outgoing traffic above this
           rate will be dropped.</para>
 
-          <para> Use kbit or kbps(for Kilobytes per second) for speed, and
-          make sure there is NO space between the number and the unit.</para>
+          <para>Use kbit or kbps(for Kilobytes per second) for speed, and make
+          sure there is NO space between the number and the unit.</para>
         </listitem>
       </varlistentry>
     </variablelist>
diff --git a/manpages/shorewall-tcrules.xml b/manpages/shorewall-tcrules.xml
index 03cb8c1b4..51195aa82 100644
--- a/manpages/shorewall-tcrules.xml
+++ b/manpages/shorewall-tcrules.xml
@@ -170,7 +170,7 @@
               the line will be attached as a comment to the Netfilter rule(s)
               generated by the following entries. The comment will appear
               delimited by "/* ... */" in the output of <command>shorewall
-              show mangle</command> </para>
+              show mangle</command></para>
 
               <para>To stop the comment from being attached to further rules,
               simply include COMMENT on a line by itself.</para>
@@ -218,7 +218,7 @@
           an address (e.g., eth1:192.168.1.0/24). If the <emphasis
           role="bold">MARK</emphasis> column specificies a classification of
           the form <emphasis>major</emphasis>:<emphasis>minor</emphasis> then
-          this column may also contain an interface name. </para>
+          this column may also contain an interface name.</para>
         </listitem>
       </varlistentry>
 
@@ -241,7 +241,7 @@
         <term><emphasis role="bold">PORT(S)</emphasis></term>
 
         <listitem>
-          <para> Destination Ports. A comma-separated list of Port names (from
+          <para>Destination Ports. A comma-separated list of Port names (from
           services(5)), <emphasis>port number</emphasis>s or <emphasis>port
           range</emphasis>s; if the protocol is <emphasis
           role="bold">icmp</emphasis>, this column is interpreted as the
@@ -337,9 +337,9 @@
         <term>TEST</term>
 
         <listitem>
-          <para> Defines a test on the existing packet or connection mark. The
-          rule will match only if the test returns true. Tests have the format
-          </para>
+          <para>Defines a test on the existing packet or connection mark. The
+          rule will match only if the test returns true. Tests have the
+          format</para>
 
           <para>[<emphasis
           role="bold">!</emphasis>]<emphasis>value</emphasis>[/<emphasis>mask</emphasis>][<emphasis
@@ -436,8 +436,7 @@
           are P2P packets, we mark the entire connection as P2P if any of the
           packets are determined to match.</para>
 
-          <para>We assume packet/connection mark 0 to means
-          unclassified.</para>
+          <para>We assume packet/connection mark 0 means unclassified.</para>
 
           <programlisting>       #MARK/    SOURCE    DEST         PROTO   PORT(S)       SOURCE  USER    TEST
        #CLASSIFY                                              PORT(S)
diff --git a/manpages/shorewall-zones.xml b/manpages/shorewall-zones.xml
index 19a9a28c8..15d54425f 100644
--- a/manpages/shorewall-zones.xml
+++ b/manpages/shorewall-zones.xml
@@ -96,7 +96,7 @@ c:a,b     ipv4</programlisting>
 
               <listitem>
                 <para>Communication with all zone hosts is encrypted. Your
-                kernel and iptables must include polic match support.</para>
+                kernel and iptables must include policy match support.</para>
               </listitem>
             </varlistentry>
 
@@ -105,10 +105,11 @@ c:a,b     ipv4</programlisting>
 
               <listitem>
                 <para>Designates the firewall itself. You must have exactly
-                one 'firewall' zone. No options ar permitted with a 'firewall'
-                zone. The name that you enter in the ZONE column will be
-                stored in the shell variable $FW which you may use in other
-                configuration files to designate the firewall zone.</para>
+                one 'firewall' zone. No options are permitted with a
+                'firewall' zone. The name that you enter in the ZONE column
+                will be stored in the shell variable $FW which you may use in
+                other configuration files to designate the firewall
+                zone.</para>
               </listitem>
             </varlistentry>
           </variablelist>