From fb2036243368c0db91997a7ce8f11de70d9f85ec Mon Sep 17 00:00:00 2001
From: bhargavbh <2bhargav5@gmail.com>
Date: Mon, 10 Jun 2024 10:02:41 +0200
Subject: [PATCH] state requet substream updated

---
 docs/chap-networking.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/chap-networking.md b/docs/chap-networking.md
index 2b81b6c87..8f97b36c3 100644
--- a/docs/chap-networking.md
+++ b/docs/chap-networking.md
@@ -475,7 +475,7 @@ See the synchronization chapter for more information ([Chapter -chap-num-ref-](c
 
 A **state request** is sent to a peer to request the state at a specified block. The message is a single 32-byte Blake2 hash which indicates the block from which the sync should start.
 
-Depending on what substream is used, the remote peer either sends back a state response ([Definition -def-num-ref-](chap-networking#defn-msg-state-response)) on the `/dot/sync/2` substream or a warp sync proof ([Definition -def-num-ref-](chap-networking#defn-warp-sync-proof)) on the `/dot/sync/warp`.
+Depending on what substream is used, the remote peer either sends back a state response ([Definition -def-num-ref-](chap-networking#defn-msg-state-response)) on the `/dot/state/2` substream or a warp sync proof ([Definition -def-num-ref-](chap-networking#defn-warp-sync-proof)) on the `/dot/sync/warp`.
 
 :::
 ###### Definition -def-num- State Response {#defn-msg-state-response}