From b0f82cce154ee85b24a5fe59b06e77ad4f245cf8 Mon Sep 17 00:00:00 2001 From: braginini Date: Thu, 19 Jun 2025 10:34:49 +0200 Subject: [PATCH] Clarify traffic events wording --- src/pages/how-to/traffic-events-logging.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/pages/how-to/traffic-events-logging.mdx b/src/pages/how-to/traffic-events-logging.mdx index f75fb6e4..d8d1f5bb 100644 --- a/src/pages/how-to/traffic-events-logging.mdx +++ b/src/pages/how-to/traffic-events-logging.mdx @@ -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.