From 415b03d06d0ca029c0f6de077fb55451967b5120 Mon Sep 17 00:00:00 2001 From: Mauro Servienti Date: Tue, 31 Dec 2024 17:08:58 +0100 Subject: [PATCH] minor review changes --- nservicebus/messaging/routing_commands_core_[7,).partial.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nservicebus/messaging/routing_commands_core_[7,).partial.md b/nservicebus/messaging/routing_commands_core_[7,).partial.md index a9d9d0fbd5a..c0d98cf5b4c 100644 --- a/nservicebus/messaging/routing_commands_core_[7,).partial.md +++ b/nservicebus/messaging/routing_commands_core_[7,).partial.md @@ -1,5 +1,5 @@ -Command routing can be configured in code. The routing API is attached to the transport configuration object because some routing APIs are transport-specific. The routes can be specified at assembly, namespace or specific type levels. +Command routing can be configured in code. The routing API is attached to the transport configuration object because some routing APIs are transport-specific. The routes can be specified at assembly, namespace, or specific type levels. snippet: Routing-Logical -The routing engine prevents ambiguous routes so if route information comes from more than one source (e.g. code API and configuration file) the user has to make sure the type specifications do not overlap. If they do overlap, an exception will be thrown preventing the endpoint from starting up. +The routing engine prevents ambiguous routes, so if route information comes from more than one source (e.g., code API, and configuration file), the user must ensure that the type specifications do not overlap. If they do, an exception will be thrown, preventing the endpoint from starting up.