[PATCH v5 4/4] doc: minor improvements the `reject` statement

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

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

diff --git a/doc/nft.txt b/doc/nft.txt
index 4a90f020..006086e6 100644
--- a/doc/nft.txt
+++ b/doc/nft.txt
@@ -572,6 +572,7 @@ table inet filter {
 nft delete rule inet filter input handle 5
 -------------------------
 
+[[OVERALL_EVALUATION_OF_THE_RULESET]]
 OVERALL EVALUATION OF THE RULESET
 ---------------------------------
 This is a summary of how the ruleset is evaluated.
diff --git a/doc/statements.txt b/doc/statements.txt
index e1d8552c..1b05b4b6 100644
--- a/doc/statements.txt
+++ b/doc/statements.txt
@@ -1,3 +1,4 @@
+[[VERDICT_STATEMENTS]]
 VERDICT STATEMENTS
 ~~~~~~~~~~~~~~~~~~
 The verdict statements alter control flow in the ruleset and issue policy
@@ -222,10 +223,11 @@ ____
                  *tcp reset*
 ____
 
-A reject statement is used to send back an error packet in response to the
-matched packet otherwise it is equivalent to drop so it is a terminating
-statement, ending rule traversal. This statement is only valid in base chains
-using the *prerouting*, *input*,
+A reject statement tries to send back an error packet in response to the matched
+packet and then interally issues a *drop* verdict.
+It’s thus a terminating statement with all consequences of the latter (see
+<<OVERALL_EVALUATION_OF_THE_RULESET>> respectively <<VERDICT_STATEMENTS>>).
+This statement is only valid in base chains using the *prerouting*, *input*,
 *forward* or *output* hooks, and user-defined chains which are only called from
 those chains.
 
-- 
2.51.0