diff --git a/docs/architecture/index.md b/docs/architecture/index.md
index e6637b46f..4cf4724d1 100644
--- a/docs/architecture/index.md
+++ b/docs/architecture/index.md
@@ -149,7 +149,7 @@ Can connect both the real-time and historical data to allow users to query acros
 
     Return sensible errors when queries fail.
 
-    Use the deferred-response feature (V3.6) to avoid additional coding on the side of connecting non-kdb+ processes.
+    Use the [deferred-response]((../basics/internal.md#-30x-deferred-response) feature (V3.6) to avoid additional coding on the side of connecting non-kdb+ processes.
 
     [Load-management](../kb/load-balancing.md): round-robin might not be the best option for your system. 
     Consider other options specific to your APIs and load.
diff --git a/docs/kb/deferred-response.md b/docs/kb/deferred-response.md
index 11cb084a6..13f3660b9 100644
--- a/docs/kb/deferred-response.md
+++ b/docs/kb/deferred-response.md
@@ -1,6 +1,6 @@
 ---
 title: Deferred response – Knowledge Base – kdb+ and q documentation
-description: Ideally, for concurrency, all messaging would be async. However, sync messaging is a convenient paradigm for client apps. Hence -30!x was added as a feature in V3.6, allowing processing of a sync message to be ‘suspended’ to allow other messages to be processed prior to sending a response message. 
+description: Ideally, for concurrency, all messaging would be async. However, sync messaging is a convenient paradigm for client apps. Hence [-30!x](../basics/internal.md#-30x-deferred-response) was added as a feature in V3.6, allowing processing of a sync message to be ‘suspended’ to allow other messages to be processed prior to sending a response message. 
 author: Charles Skelton
 keywords: async, concurrency, deferred, kdb+_, q, response, sync
 ---
@@ -64,5 +64,8 @@ callback:{[clientHandle;result]
 
 :fontawesome-regular-hand-point-right: 
 Basics: [Internal `-30!x`](../basics/internal.md#-30x-deferred-response)  
+:fontawesome-regular-hand-point-right:
+Blog: [Deferred Response](https://kx.com/blog/kdb-q-insights-deferred-response/)
+<br>
 [Namespace `.z`](../ref/dotz.md)
 
diff --git a/docs/wp/ipc/index.md b/docs/wp/ipc/index.md
index feea6fbf8..108b310ea 100644
--- a/docs/wp/ipc/index.md
+++ b/docs/wp/ipc/index.md
@@ -377,7 +377,7 @@ q)h"a"
 
 !!! tip "Deferred response" 
 
-    [Deferred reponse](../../kb/deferred-response.md) with `-30!` allows a server to defer the response to a synchronous query, allowing other messages to be processed before responding. This is useful where synchronous messaging is necessary on the client side. 
+    [Deferred reponse](../../kb/deferred-response.md) with [`-30!`](../../basics/internal.md#-30x-deferred-response) allows a server to defer the response to a synchronous query, allowing other messages to be processed before responding. This is useful where synchronous messaging is necessary on the client side. 
 
     An example implementation of deferred sync message handling is discussed in the blog [kdb+/q Insights: Deferred Response](https://kx.com/blog/kdb-q-insights-deferred-response/).
 
diff --git a/mkdocs.yml b/mkdocs.yml
index 90da43c94..dba73bccb 100644
--- a/mkdocs.yml
+++ b/mkdocs.yml
@@ -456,6 +456,7 @@ nav:
         - Overview: basics/ipc.md
         - Callbacks: kb/callbacks.md
         - Listening port: basics/listening-port.md
+        - Deferred response: kb/deferred-response.md
         - Named pipes: kb/named-pipes.md
         - Serialization examples: kb/serialization.md
         - Server calling client: kb/server-calling-client.md
@@ -474,7 +475,6 @@ nav:
         - Monitor & control execution: kb/using-dotz.md
       - Coding:
         - Data visualization (WP): wp/data-visualization/index.md
-        - Deferred response: kb/deferred-response.md
         - Geospatial indexing: kb/geospatial.md
         - Linear programming: kb/lp.md
         - Multithreaded input: kb/multithreaded-input.md