From 799a7ead9dc2dae051966fb51c6a47b8275b67ed Mon Sep 17 00:00:00 2001
From: Teriuihi <38841986+Teriuihi@users.noreply.github.com>
Date: Sun, 15 May 2022 20:27:30 +0200
Subject: [PATCH] added/fixed try-unlock-result

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index ddf635d..a45bf92 100644
--- a/README.md
+++ b/README.md
@@ -15,7 +15,7 @@
 		<code>check-lock</code>: Check if a data entry is locked, it will send the result back as a boolean on <code>check-lock-result</code>
 	</li>
 	<li>
-		<code>try-unlock</code>: Attempt to unlock a data entry it will send a boolean back on <code>try-lock-result</code>
+		<code>try-unlock</code>: Attempt to unlock a data entry it will send a boolean back on <code>try-unlock-result</code>
     If succesfull this will check if there is a queued lock for this data entry and if so lock that for that server and notify it on
     <code>locked-queued-lock</code> with information on what the data was
 	</li>
@@ -29,7 +29,7 @@
 			<li>UTF: data (data to lock/check/unlock)</li>
 		</ul>
 	</li>
-	<li><code>try-lock-result</code>/<code>check-lock-result</code>
+	<li><code>try-lock-result</code>/<code>try-unlock-result</code>/<code>check-lock-result</code>
 		<ul>
     	<li>UTF: sub channel (the sub channel)
     	<li>boolean: success (if the lock/unlock succeeded or not or if the data was locked or not)</li>