Fix doc

README.md

@@ -21,7 +21,7 @@ Here is a list of guiding principles that Revm follows.
 
 * **EVM compatibility and stability** - this goes without saying but it is nice to put it here. In the blockchain industry, stability is the most desired attribute of any system.
 * **Speed** - is one of the most important things and most decisions are made to complement this.
-* **Simplicity** - simplification of internals so that it can be easily understood and extended, and interface that can be easily used or integrated into other projects.
+* **Simplicity** - simplification of internals so that they can be easily understood and extended, and interface that can be easily used or integrated into other projects.
 * **interfacing** - `[no_std]` so that it can be used as wasm lib and integrate with JavaScript and cpp binding if needed.
 
 # Project
@@ -152,6 +152,6 @@ mdbook serve documentation
 
 # Contact
 
-There is public telegram group: https://t.me/+Ig4WDWOzikA3MzA0
+There is a public telegram group: https://t.me/+Ig4WDWOzikA3MzA0
 
 Or if you want to contact me directly, here is my email: dragan0rakita@gmail.com and telegram: https://t.me/draganrakita

documentation/src/crates/interpreter/instruction_result.md

@@ -8,7 +8,7 @@ The `instruction_result.rs` module of this Rust EVM implementation includes the
 
 - `SuccessOrHalt` Enum
 
-    The `SuccessOrHalt` enum represents the outcome of a transaction execution, distinguishing successful operations, reversion, halting conditions, fatal external errors, and internal continuation. It also provides several methods to check the kind of result and to extract the value of the successful evaluation or halt.
+    The `SuccessOrHalt` enum represents the outcome of transaction execution, distinguishing successful operations, reversion, halting conditions, fatal external errors, and internal continuation. It also provides several methods to check the kind of result and to extract the value of the successful evaluation or halt.
 
 - `From<InstructionResult> for SuccessOrHalt` Implementation
 

documentation/src/crates/primitives/kzg.md

@@ -1,6 +1,6 @@
 # KZG 
 
-With the introduction of [EIP4844](https://eips.ethereum.org/EIPS/eip-4844), this use of blobs for a more efficient short term storage is employed, the validity of this blob stored in the consensus layer is verified using the `Point Evaluation` pre-compile, a fancy way of verifying that and evaluation at a given point of a committed polynomial is valid, on a much bigger scale, implies that `Data is Available`.
+With the introduction of [EIP4844](https://eips.ethereum.org/EIPS/eip-4844), this use of blobs for a more efficient short-term storage is employed, the validity of this blob stored in the consensus layer is verified using the `Point Evaluation` pre-compile, a fancy way of verifying that and evaluation at a given point of a committed polynomial is valid, on a much bigger scale, implies that `Data is Available`.
 
 This module houses;
 

documentation/src/crates/primitives/precompile.md

@@ -6,4 +6,4 @@ This module implements precompiled contracts in the EVM, adding a layer of pre-s
 
 `StandardPrecompileFn` and `CustomPrecompileFn`: These are type aliases for function pointers. Both functions take a byte slice and a `u64` (probably the available gas) as arguments and return a `PrecompileResult`. The naming suggests that the former refers to built-in precompiled contracts, while the latter may refer to custom, user-defined contracts.
 
-`PrecompileError`: This is an enumeration (enum) which describes the different types of errors that could occur while executing a precompiled contract. The listed variants suggest these errors are related to gas consumption, `Blake2` hash function, modular exponentiation ("`Modexp`"), and `Bn128`, which is a specific elliptic curve used in cryptography.
+`PrecompileError`: This is an enumeration (enum) that describes the different types of errors that could occur while executing a precompiled contract. The listed variants suggest these errors are related to gas consumption, `Blake2` hash function, modular exponentiation ("`Modexp`"), and `Bn128`, which is a specific elliptic curve used in cryptography.