Update docs/internal/GeneralArchitectureGuide.md

zhubotang-wq · DiannaHohensee · web-flow · commit b833f7e449fa · 2025-09-29T13:51:59.000-07:00
Co-authored-by: Dianna Hohensee &lt;artemisapple@gmail.com&gt;
diff --git a/docs/internal/GeneralArchitectureGuide.md b/docs/internal/GeneralArchitectureGuide.md
@@ -110,7 +110,7 @@ are coordinated.
 >
 > [TransportAction] can also be initiated through peer-to-peer communication between nodes. In such cases, the [InboundHandler]
 > locates the appropriate [TransportAction] by consulting the [NamedRegistry], then invokes the [TransportAction]'s handleExecution() method. When a [TransportAction]
-> is registered, it can specify an executor to control how the action is run. One option is the DIRECT_EXECUTOR_SERVICE, which executes the
+> is registered, it can specify an executor to control how the action is run. One option is the `DIRECT_EXECUTOR_SERVICE`, which executes the
 > action on the calling thread. However, this should be used with caution—it's only appropriate when the action is lightweight.
 > Otherwise, it risks blocking the peer-to-peer I/O thread, potentially degrading responsiveness and causing the node to become unresponsive.
 > If [TransportAction] elects a separate executor, [InboundHandler] performs message deserialization before delegating execution to the executor,

Original file line number	Diff line number	Diff line change
`@@ -110,7 +110,7 @@ are coordinated.`
`110`	`110`	`>`
`111`	`111`	`> [TransportAction] can also be initiated through peer-to-peer communication between nodes. In such cases, the [InboundHandler]`
`112`	`112`	`> locates the appropriate [TransportAction] by consulting the [NamedRegistry], then invokes the [TransportAction]'s handleExecution() method. When a [TransportAction]`
`113`		`-> is registered, it can specify an executor to control how the action is run. One option is the DIRECT_EXECUTOR_SERVICE, which executes the`
	`113`	+> is registered, it can specify an executor to control how the action is run. One option is the `DIRECT_EXECUTOR_SERVICE`, which executes the
`114`	`114`	`> action on the calling thread. However, this should be used with caution—it's only appropriate when the action is lightweight.`
`115`	`115`	`> Otherwise, it risks blocking the peer-to-peer I/O thread, potentially degrading responsiveness and causing the node to become unresponsive.`
`116`	`116`	`> If [TransportAction] elects a separate executor, [InboundHandler] performs message deserialization before delegating execution to the executor,`