From c46938bc35a8d6e9e31d10ee6bb0f631fea4457e Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Fri, 7 Jun 2019 08:57:42 -0500 Subject: [PATCH] Update noecho.md --- developer/connecting/noecho.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developer/connecting/noecho.md b/developer/connecting/noecho.md index f206678..1ba5767 100644 --- a/developer/connecting/noecho.md +++ b/developer/connecting/noecho.md @@ -2,7 +2,7 @@ By default a NATS connection will echo messages if the connection also has interest in the published subject. This means that if a publisher on a connection sends a message to a subject any subscribers on that same connection will receive the message. Clients can opt to turn off this behavior, such that regardless of interest the message will not be delivered to subscribers on the same connection. -The NoEcho option can be useful in BUS patterns where all applications subsribe and publish to the same subject. Usually a publish represents a state change that the application already knows about, so in the case that the application opublishes an updated it does not need to process the update itself. +The NoEcho option can be useful in BUS patterns where all applications subscribe and publish to the same subject. Usually a publish represents a state change that the application already knows about, so in the case where the application publishes an update it does not need to process the update itself.
digraph {