Incorporate corrections

2 files changed, 4 insertions, 4 deletions

diff --git a/docs/control-structures.rst b/docs/control-structures.rst
index c2db523e..d3144c86 100644
--- a/docs/control-structures.rst
+++ b/docs/control-structures.rst
@@ -76,8 +76,8 @@ parentheses at the end perform the actual call.
     do just about anything. Be prepared in case it calls into other contracts of
     your system or even back into the calling contract before the first
     call returns. This means
-    that the called contract can change the state variables of the calling contract
-    via its functions. Write your functions in a way that such that, for example, calls to
+    that the called contract can change state variables of the calling contract
+    via its functions. Write your functions in a way that, for example, calls to
     external functions happen after any changes to state variables in your contract
     so your contract is not vulnerable to a recursive call exploit.
 
diff --git a/docs/security-considerations.rst b/docs/security-considerations.rst
index 726b8a2a..ac24f5cb 100644
--- a/docs/security-considerations.rst
+++ b/docs/security-considerations.rst
@@ -129,7 +129,7 @@ Callstack Depth
 ===============
 
 External function calls can fail any time because they exceed the maximum
-call stack of 1023. In such situations, Solidity throws an exception.
+call stack of 1024. In such situations, Solidity throws an exception.
 Malicious actors might be able to force the call stack to a high value
 before they interact with your contract.
 
@@ -185,7 +185,7 @@ because of the re-entrancy problem explained above.
 Note that, also, calls to known contracts might in turn cause calls to
 unknown contracts, so it is probably better to just always apply this pattern.
 
-Include a Fail-safe Mode
+Include a Fail-Safe Mode
 ========================
 
 While making your system fully decentralised will remove any intermediary,