From 277f37407592f0d035dd525bc1321bce06fe9478 Mon Sep 17 00:00:00 2001 From: Phil Sutter Date: Tue, 7 Aug 2018 13:15:34 +0200 Subject: xtables: Spelling fixes in xtables-monitor Fix a few minor spelling issues in xtables-monitor help output and man page. While being at it, change 'ipv4' and 'ipv6' to 'IPv4' and 'IPv6', respectively. Signed-off-by: Phil Sutter Signed-off-by: Florian Westphal --- iptables/xtables-monitor.8.in | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'iptables/xtables-monitor.8.in') diff --git a/iptables/xtables-monitor.8.in b/iptables/xtables-monitor.8.in index 202842b9..b647a79e 100644 --- a/iptables/xtables-monitor.8.in +++ b/iptables/xtables-monitor.8.in @@ -25,10 +25,10 @@ Watch for trace events generated by packets that have been tagged using the TRACE target. .TP \fB\-4\fP -Restrict output to ipv4. +Restrict output to IPv4. .TP \fB\-6\fP -Restrict output to ipv6. +Restrict output to IPv6. .SH EXAMPLE OUTPUT .TP .B xtables-monitor \-\-trace @@ -55,10 +55,10 @@ PREROUTING chain, and is returning, followed by use the chain policy to make acc decision (the example shows accept being applied). The fifth line shows that the packet leaves the filter INPUT chain, i.e., no rules in the filter tables INPUT chain matched the packet. -It then got DROPPED by the policy of the INPUT table, as hown by line six. +It then got DROPPED by the policy of the INPUT table, as shown by line six. The last line shows another packet arriving \-\- the packet id is different. -When using the TRACE target, it is usally a good idea to only select packets +When using the TRACE target, it is usually a good idea to only select packets that are relevant, for example via .nf iptables \-t raw \-A PREROUTING \-p tcp \-\-dport 80 \-\-syn \-m limit \-\-limit 1/s \-j TRACE -- cgit v1.2.3