From ba5b7c780a8d75abe788310f5f6e73dc7807033f Mon Sep 17 00:00:00 2001
From: Kurman Karabukaev <74940256+kurman@users.noreply.github.com>
Date: Wed, 6 Mar 2024 22:48:12 -0800
Subject: [PATCH] Update chapter2.md

More details on how router will respond to the right client (router and dealer utilize envelop)
---
 site/content/docs/chapter2.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/site/content/docs/chapter2.md b/site/content/docs/chapter2.md
index 6c88f947..999e9a1f 100644
--- a/site/content/docs/chapter2.md
+++ b/site/content/docs/chapter2.md
@@ -547,7 +547,9 @@ And here is the broker, which properly handles multipart messages:
 #---------#   #---------#   #---------#
 {{< /textdiagram >}}
 
-Using a request-reply broker makes your client/server architectures easier to scale because clients don't see workers, and workers don't see clients. The only static node is the broker in the middle.
+Using a request-reply broker makes your client/server architectures easier to scale because clients don't see workers, and workers don't see clients. The only static node is the broker in the middle. 
+
+You may wonder how a response is routed back to the right client. Router uses envelop for the message that has info on the client to the dealer and dealer response will include envelope that will be used to map the response back to the client.
 
 ### ZeroMQ's Built-In Proxy Function {#ZeroMQ-s-Built-In-Proxy-Function}