diff --git a/cairo/kakarot-ssj/docs/general/local_state.md b/cairo/kakarot-ssj/docs/general/local_state.md
index 038ca8cfb..c10e9dadd 100644
--- a/cairo/kakarot-ssj/docs/general/local_state.md
+++ b/cairo/kakarot-ssj/docs/general/local_state.md
@@ -19,7 +19,7 @@ from using dicts in self-referring data structures, instead of having one state
 per execution context that we could merge into the parent state if the context
 exits successfully or discard if the context reverts, we have one global `State`
 structs that achieves the same behavior by tracking transactional changes, which
-refers to the changes made inside the current transaction as a whole, and a
+refers to the changes made inside the current transaction as a whole, and 
 contextual changes, which refers to changes made inside the current execution
 context.
 
diff --git a/cairo/kakarot-ssj/docs/general/machine.md b/cairo/kakarot-ssj/docs/general/machine.md
index efc8f6d07..1c31a8c1c 100644
--- a/cairo/kakarot-ssj/docs/general/machine.md
+++ b/cairo/kakarot-ssj/docs/general/machine.md
@@ -4,7 +4,7 @@ The EVM is a stack-based computer responsible for the execution of EVM bytecode.
 It has two context-bound data structures: the stack and the memory. The stack is
 a 256bit-words based data structure used to store and retrieve intermediate
 values during the execution of opcodes. The memory is a byte-addressable data
-structure organized into 32-byte words used a volatile space to store data
+structure organized into 32-byte words used volatile space to store data
 during execution. Both the stack and the memory are initialized empty at the
 start of a call context, and destroyed when a call context ends.