From cd1428c8fb828542ff314b6a8bd62a8ea4f67659 Mon Sep 17 00:00:00 2001
From: Kamil Chmielewski <45183584+ChmielewskiKamil@users.noreply.github.com>
Date: Fri, 23 Sep 2022 14:06:13 +0200
Subject: [PATCH] docs: fix typo

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

diff --git a/README.md b/README.md
index 13761f8..da79a87 100644
--- a/README.md
+++ b/README.md
@@ -422,7 +422,7 @@ A common defensive programming technique that is useful in enforcing correct sta
 
 In particular, there is one apparent *invariant*, that may be tempting to use
 but can in fact be manipulated by external users (regardless of the rules put
-in place in the smart contract) .This is the current ether stored in the
+in place in the smart contract). This is the current ether stored in the
 contract. Often when developers first learn Solidity they have the
 misconception that a contract can only accept or obtain ether via payable
 functions. This misconception can lead to  contracts that have false