From 77436c651d2a1965719c5cf53d5a9c207d562a52 Mon Sep 17 00:00:00 2001
From: spaced4ndy <8711996+spaced4ndy@users.noreply.github.com>
Date: Tue, 21 Oct 2025 18:29:19 +0400
Subject: [PATCH] formatting

---
 docs/rfcs/2025-10-20-chat-relays.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/rfcs/2025-10-20-chat-relays.md b/docs/rfcs/2025-10-20-chat-relays.md
index ae0eb24fcc..4ccd3c48aa 100644
--- a/docs/rfcs/2025-10-20-chat-relays.md
+++ b/docs/rfcs/2025-10-20-chat-relays.md
@@ -85,7 +85,7 @@ Notes:
     - Step 3. Add link to group profile - local, automatic upon synchronous response from step 2. No recovery needed.
     - Step 4. Choose chat relays - TBC automatic or user action? User action: confirm to auto-select, or let user choose?
       This action is local but user action should be remembered - at this point `group_relays` records should be created and associated with group, in status `CRSNew`.
-      Further recovery can be done per relay record based on status.
+      Further recovery can be done per relay record based on status:
       - Step 5. Contact request to relay. Contact request should be done via asynchronous agent action. New connection (for contact request) should be associated with relay, relay status moves to `CRSInvited`.
         - Member connection, link `group_members` to `group_relays`.
         Recovery from `CRSInvited` status is not needed, at this point owner waits for relay response.