Update docs/internal/GeneralArchitectureGuide.md

zhubotang-wq · DiannaHohensee · web-flow · commit 3c91c6fd3762 · 2025-09-29T13:51:07.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
@@ -102,7 +102,7 @@ are coordinated.
 > `Rest*Action`'s `prepareRequest` implementation, it should specify the `ActionType` being invoked which can then be used to locate
 > the `Transport*Action` class that handles it.
 >
-> A netty [EventLoop] thread handles the initial steps of a Rest*Action request lifecycle such as decoding, validation and routing.
+> A netty [EventLoop] thread handles the initial steps of a `Rest*Action` request lifecycle such as decoding, validation and routing.
 > Upon entry into the "transport layer", [NodeClient] delegates the decision of execution to individual [TransportAction]. Each action
 > determines whether to execute synchronously on invoking thread-an approach reserved for lightweight processing-or to dispatch execution to an appropriate
 > thread pool, which is recommended practice for heavy workloads. Comprehensive mechanisms are available for propagating [ThreadContext] when tasks

Original file line number	Diff line number	Diff line change
`@@ -102,7 +102,7 @@ are coordinated.`
`102`	`102`	> `Rest*Action`'s `prepareRequest` implementation, it should specify the `ActionType` being invoked which can then be used to locate
`103`	`103`	> the `Transport*Action` class that handles it.
`104`	`104`	`>`
`105`		`-> A netty [EventLoop] thread handles the initial steps of a Rest*Action request lifecycle such as decoding, validation and routing.`
	`105`	+> A netty [EventLoop] thread handles the initial steps of a `Rest*Action` request lifecycle such as decoding, validation and routing.
`106`	`106`	`> Upon entry into the "transport layer", [NodeClient] delegates the decision of execution to individual [TransportAction]. Each action`
`107`	`107`	`> determines whether to execute synchronously on invoking thread-an approach reserved for lightweight processing-or to dispatch execution to an appropriate`
`108`	`108`	`> thread pool, which is recommended practice for heavy workloads. Comprehensive mechanisms are available for propagating [ThreadContext] when tasks`