Skip to content

Commit b0f82cc

Browse files
committed
Clarify traffic events wording
1 parent 89ed145 commit b0f82cc

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/pages/how-to/traffic-events-logging.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ Note the `ROUTER` column in the table, which identifies the routing peer respons
103103
In the event of a blocked connection, the initiating peer logs the connection attempt, while the routing peer records the blocked event.
104104
The screenshot below demonstrates this behavior: the routing peer blocks a connection to the network resource `CRM` because
105105
the policy `IT Admins to AWS Servers` does not permit connections over the `HTTP` protocol on port `6432`.
106-
You can see multiple blocked events from the routing peer, which indicates that the initiating peer `Alice` attempted to connect multiple times
106+
You can see multiple blocked events reported by the routing peer, which indicates that the initiating peer `Alice` attempted to connect multiple times
107107
in one TCP session, but the routing peer blocked all attempts.
108108

109109
<p>

0 commit comments

Comments
 (0)