From: Phil Sutter <phil@nwl.cc>
Date: Fri, 11 May 2018 12:20:35 +0000 (+0200)
Subject: nft.8: Drop misleading adjective 'absolute'
X-Git-Tag: v0.9.0~63
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=3b71baba43fa1ce53fa034257b17954e05c230fb;p=thirdparty%2Fnftables.git

nft.8: Drop misleading adjective 'absolute'

Discussion showed that rule index may be interpreted as being absolute
or relative, so just drop this adjective without replacement.

Signed-off-by: Phil Sutter <phil@nwl.cc>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
---

diff --git a/doc/nft.xml b/doc/nft.xml
index ab94bff4..05193e67 100644
--- a/doc/nft.xml
+++ b/doc/nft.xml
@@ -918,7 +918,7 @@ add table inet mytable
 		<para>
 			The <literal>add</literal> and <literal>insert</literal> commands support an optional
 			location specifier, which is either a <replaceable>handle</replaceable> of an existing
-			rule or an absolute <replaceable>index</replaceable> (starting at zero).  Internally,
+			rule or an <replaceable>index</replaceable> (starting at zero).  Internally,
 			rule locations are always identified by <replaceable>handle</replaceable> and the
 			translation from <replaceable>index</replaceable> happens in userspace. This has two
 			potential implications in case a concurrent ruleset change happens after the translation