diff --git a/manpages/shorewall-rules.xml b/manpages/shorewall-rules.xml
index d1813c32f..14fcae265 100644
--- a/manpages/shorewall-rules.xml
+++ b/manpages/shorewall-rules.xml
@@ -181,7 +181,7 @@
- ACCEPT!
+ ACCEPT!
like ACCEPT but exempts the rule from being suppressed
@@ -210,7 +210,7 @@
- DROP!
+ DROP!
like DROP but exempts the rule from being suppressed by
@@ -229,7 +229,7 @@
- REJECT!
+ REJECT!
like REJECT but exempts the rule from being suppressed
@@ -327,7 +327,7 @@
- CONTINUE!
+ CONTINUE!
like CONTINUE but exempts the rule from being suppressed
@@ -356,7 +356,7 @@
- QUEUE!
+ QUEUE!
like QUEUE but exempts the rule from being suppressed by
@@ -379,7 +379,7 @@
- NFQUEUE!
+ NFQUEUE!
like NFQUEUE but exempts the rule from being suppressed
@@ -615,11 +615,11 @@
IP/MAC/subnet address as described above (e.g., loc:eth1:192.168.1.5).
- It is important to note that when using
- Shorewall-shell and specifying an address list that will
- be split (i.e., a comma separated list), there is a subtle behavior
- which has the potential to cause confusion. Consider the two
- examples below:
+ It is important to note that when using Shorewall-shell and specifying an
+ address list that will be split (i.e., a comma separated list),
+ there is a subtle behavior which has the potential to cause
+ confusion. Consider the two examples below:
Examples:
@@ -645,9 +645,10 @@
+
That is, the interface name must be explicitly stated for
- each member of the comma separated list. Again, this distinction
+ each member of the comma separated list. Again, this distinction
in behavior only occurs when using
Shorewall-shell.
@@ -1266,4 +1267,4 @@
shorewall-tcclasses(5), shorewall-tcdevices(5), shorewall-tcrules(5),
shorewall-tos(5), shorewall-tunnels(5), shorewall-zones(5)
-
+
\ No newline at end of file