From ad7e9d34307cbef59bea55a77ed75dc0e6be6d8c Mon Sep 17 00:00:00 2001
From: John Carvalho <18273620+BitcoinErrorLog@users.noreply.github.com>
Date: Mon, 17 Jun 2024 12:44:55 +0100
Subject: [PATCH] Update readme.md

---
 readme.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/readme.md b/readme.md
index 27effca..7d18dd3 100644
--- a/readme.md
+++ b/readme.md
@@ -49,7 +49,7 @@ Users can make signed payment requests to credit issuers. Upon receiving an auth
 
 Credit holders can also settle with the issuer by including extra Paykit endpoints that are simply other Atomicity user keys. This would enable the issuer to transfer credit from one user to another compatible user/key. 
 
-**Routing, Compatible Users **
+**Routing, Compatible Users**
 
 Atomicity utilizes the tagging method, of/like Slashtags, to establish whitelistings of keys, along with credit limits the peer is willing to receive and/or issue to each peer key. Users could also assign default settings for degrees of separation (WoT distance), and effectively establish mutual credit channels with states.