[PATCH v2 3/7] doc: minor improvements with respect to the term “ruleset”

[Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>]

Statements are elements of rules. Non-terminal statement are in particular
passive with respect to their rules (and thus automatically with respect to the
whole ruleset).

In “Continue ruleset evaluation”, it’s not necessary to mention the ruleset as
it’s obvious that the evaluation of the current chain will be continued.

Signed-off-by: Christoph Anton Mitterer <mail@christoph.anton.mitterer.name>
---
 doc/nft.txt        | 6 +++---
 doc/statements.txt | 4 ++--
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/nft.txt b/doc/nft.txt
index 88c08618..a32fb10c 100644
--- a/doc/nft.txt
+++ b/doc/nft.txt
@@ -910,9 +910,9 @@ actions, such as logging, rejecting a packet, etc. +
 Statements exist in two kinds. Terminal statements unconditionally terminate
 evaluation of the current rule, non-terminal statements either only
 conditionally or never terminate evaluation of the current rule, in other words,
-they are passive from the ruleset evaluation perspective. There can be an
-arbitrary amount of non-terminal statements in a rule, but only a single
-terminal statement as the final statement.
+they are passive from the rule evaluation perspective. There can be an arbitrary
+amount of non-terminal statements in a rule, but only a single terminal
+statement as the final statement.
 
 include::statements.txt[]
 
diff --git a/doc/statements.txt b/doc/statements.txt
index f812dec8..850c32cb 100644
--- a/doc/statements.txt
+++ b/doc/statements.txt
@@ -54,8 +54,8 @@ those are not evaluated anymore for the packet.
  either the base chain or a regular chain that was reached solely via *goto*
  verdicts) end evaluation of the current base chain (and any regular chains
  called from it) using the base chain’s policy as implicit verdict.
-*continue*:: Continue ruleset evaluation with the next rule. This
- is the default behaviour in case a rule issues no verdict.
+*continue*:: Continue evaluation with the next rule. This is the default
+ behaviour in case a rule issues no verdict.
 *queue*:: Terminate ruleset evaluation and queue the packet to userspace.
 Userspace must provide a drop or accept verdict.  In case of accept, processing
 resumes with the next base chain hook, not the rule following the queue verdict.
-- 
2.51.0