[PATCH v3 6/6] 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/statements.txt | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/doc/statements.txt b/doc/statements.txt
index 61a4614d..5d34d03a 100644
--- a/doc/statements.txt
+++ b/doc/statements.txt
@@ -233,10 +233,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