From c1f4dc27924435ce3d881637e116442915ca2ede Mon Sep 17 00:00:00 2001
From: anujsharma13 <58300267+anujsharma13@users.noreply.github.com>
Date: Sun, 18 May 2025 23:51:54 +0530
Subject: [PATCH] Update README.md

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

diff --git a/README.md b/README.md
index 90d2a6aca65..47d13a0690e 100644
--- a/README.md
+++ b/README.md
@@ -478,7 +478,7 @@ With multiple copies of the same data, we are faced with options on how to synch
 
 After a write, reads may or may not see it.  A best effort approach is taken.
 
-This approach is seen in systems such as memcached.  Weak consistency works well in real time use cases such as VoIP, video chat, and realtime multiplayer games.  For example, if you are on a phone call and lose reception for a few seconds, when you regain connection you do not hear what was spoken during connection loss.
+This approach is seen in systems such as memcached.  Weak consistency works well in real time use cases such as VoIP, video chat, and realtime multiplayer games.  For example, if you are on a phone call and lose connection for a few seconds, when you regain connection you do not hear what was spoken during connection loss.
 
 ### Eventual consistency