From d55fabce9b0366f1817aaab8f48652106c49f412 Mon Sep 17 00:00:00 2001 From: Ginger Collison Date: Thu, 6 Feb 2020 11:58:32 -0600 Subject: [PATCH] Update README.md --- developing-with-nats/receiving/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developing-with-nats/receiving/README.md b/developing-with-nats/receiving/README.md index b4be18f..6fbe358 100644 --- a/developing-with-nats/receiving/README.md +++ b/developing-with-nats/receiving/README.md @@ -4,6 +4,6 @@ In general, applications can receive messages asynchronously or synchronously. R Some languages, like Go or Java, provide synchronous and asynchronous APIs, while others may only support one type of subscription. -In all cases, the process of subscribing involves having the client library tell the NATS system that an application is interested in a particular subject. When an application is done with a subscription it unsubscribes which tells the server to stop sending messages. +In all cases, the process of subscribing involves having the client library tell the NATS system that an application is interested in a particular subject. When an application is done with a subscription it unsubscribes telling the server to stop sending messages. If a connection has multiple subscriptions using identical or overlapping subjects (say `foo` and `>`), the same message will be sent to the client multiple times.