Clarify traffic events wording

This commit is contained in:
braginini
2025-06-19 10:34:49 +02:00
parent 89ed145aef
commit b0f82cce15

View File

@@ -103,7 +103,7 @@ Note the `ROUTER` column in the table, which identifies the routing peer respons
In the event of a blocked connection, the initiating peer logs the connection attempt, while the routing peer records the blocked event.
The screenshot below demonstrates this behavior: the routing peer blocks a connection to the network resource `CRM` because
the policy `IT Admins to AWS Servers` does not permit connections over the `HTTP` protocol on port `6432`.
You can see multiple blocked events from the routing peer, which indicates that the initiating peer `Alice` attempted to connect multiple times
You can see multiple blocked events reported by the routing peer, which indicates that the initiating peer `Alice` attempted to connect multiple times
in one TCP session, but the routing peer blocked all attempts.
<p>