From d364c61d291b0e81415bbbb9f622c35244b579e2 Mon Sep 17 00:00:00 2001
From: Mrinal Wadhwa <mrinal@ockam.io>
Date: Wed, 7 Feb 2024 20:40:32 +0000
Subject: [PATCH] GITBOOK-1311: change request with no subject merged in
 GitBook

---
 how-does-ockam-work.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/how-does-ockam-work.md b/how-does-ockam-work.md
index 7cc4de51..8f6c81da 100644
--- a/how-does-ockam-work.md
+++ b/how-does-ockam-work.md
@@ -50,7 +50,7 @@ ockam relay create postgres
 
 In Bank Corp’s AWS VPC, on the machine where postgres is running, create a tcp portal outlet.&#x20;
 
-When this outlet receives messages from corresponding inlets, it unwraps all [<mark style="color:blue;">routing</mark>](reference/protocols/routing.md) information and sends raw tcp connections and segments to the postgres server on localhost port _5432_. Response segments from the tcp server are wrapped with the appropriate [<mark style="color:blue;">routing</mark>](reference/protocols/routing.md) information and sent to corresponding inlets.
+When this outlet receives messages from corresponding inlets, it unwraps all [<mark style="color:blue;">routing</mark>](reference/protocols/routing.md) information and sends raw tcp connections and segments to the postgres server on localhost port _5432_. Response segments from the tcp server are wrapped in [<mark style="color:blue;">routing</mark>](reference/protocols/routing.md) information and sent to corresponding inlets.
 
 Next, create a relay in your project at address: _postgres_.