From 6c33ddd8bb96dff3f74017c915bc86fe73f96503 Mon Sep 17 00:00:00 2001
From: Attila Kovacs <attipaci@gmail.com>
Date: Tue, 3 Sep 2024 19:52:25 +0200
Subject: [PATCH] Small README edits

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

diff --git a/README.md b/README.md
index e291094..b94fccc 100644
--- a/README.md
+++ b/README.md
@@ -645,7 +645,8 @@ Execution blocks offer a fairly simple way of bunching
   Redis *redis = ...;
   RESP *result;
   
-  // Obtain the client on which to execute the block, e.g. the INTERACTIVE_CHANNEL
+  // Obtain a lock on the client on which to execute the block.
+  // e.g. the INTERACTIVE_CHANNEL
   RedisClient *cl = redisxGetClient(redis, INTERACTIVE_CHANNEL);
   
   int status = redisxLockEnabled(cl);
@@ -673,7 +674,7 @@ Execution blocks offer a fairly simple way of bunching
   ... 
 ```
 
-If at any point things don't go accoring to plan in the middle of the block, you can call `redisAbortBlockAsync()` to
+If at any point things don't go according to plan in the middle of the block, you can call `redisAbortBlockAsync()` to
 abort and discard all prior commands submitted in the execution block already.
 
 <a name="lua-script-loading-and-execution"></a>