From c29a9dbcce671fe32119ba6a45ed5a531c50cce6 Mon Sep 17 00:00:00 2001 From: Stephen Wadeley Date: Wed, 12 Jun 2013 22:43:23 +0200 Subject: man: improvements to language for flowtop.8 Signed-off-by: Stephen Wadeley Signed-off-by: Daniel Borkmann --- flowtop.8 | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'flowtop.8') diff --git a/flowtop.8 b/flowtop.8 index d11cf25..eda45e7 100644 --- a/flowtop.8 +++ b/flowtop.8 @@ -37,7 +37,7 @@ The following information will be presented in flowtop's output: * Flow port's service name heuristic * Transport protocol state machine information .PP -In order for flowtop to work, netfilter/iptables must be active resp. running +In order for flowtop to work, netfilter must be active and running on your machine, thus kernel-side connection tracking is active. .PP flowtop's intention is just to get a quick look over your active connections. @@ -47,15 +47,15 @@ instead. .SH OPTIONS .PP .SS -4, --ipv4 -Display IPv4 flows. That's default when flowtop is started without +Display IPv4 flows. That is the default when flowtop is started without any arguments. .PP .SS -6, --ipv6 -Display IPv6 flows. That's default when flowtop is started without +Display IPv6 flows. That is the default when flowtop is started without any arguments. .PP .SS -T, --tcp -Display TCP flows. That's default when flowtop is started without +Display TCP flows. That is the default when flowtop is started without any arguments. .PP .SS -U, --udp @@ -108,7 +108,7 @@ service resolution and lookup information. With a fairly high rate of connection tracking updates, flowtop can become unresponsive for short periods of time while scrolling. The right fix would be to replace flowtop's connection management backend with a better design -resp. locking approach. Still on todo. +with respect to the locking approach. This is still on the "todo" list. .PP .SH LEGAL flowtop is licensed under the GNU GPL version 2.0. -- cgit v1.2.3-54-g00ecf