chore: fix some comments

crates/interpreter/src/interpreter_action.rs

@@ -19,7 +19,7 @@ use std::boxed::Box;
 #[cfg_attr(feature = "serde", derive(serde::Serialize, serde::Deserialize))]
 pub enum InterpreterAction {
     /// CALL, CALLCODE, DELEGATECALL, STATICCALL
-    /// or EOF EXT instuction called.
+    /// or EOF EXT instruction called.
     Call { inputs: Box<CallInputs> },
     /// CREATE or CREATE2 instruction called.
     Create { inputs: Box<CreateInputs> },

crates/interpreter/src/interpreter_action/call_inputs.rs

@@ -81,7 +81,7 @@ pub enum CallScheme {
     StaticCall,
 }
 
-/// Transfered value from caller to callee.
+/// Transferred value from caller to callee.
 #[derive(Clone, Debug, PartialEq, Eq, Hash)]
 #[cfg_attr(feature = "serde", derive(serde::Serialize, serde::Deserialize))]
 pub enum TransferValue {

crates/interpreter/src/interpreter_action/eof_create_inputs.rs

@@ -5,11 +5,11 @@ use core::ops::Range;
 #[derive(Debug, Default, Clone, PartialEq, Eq)]
 #[cfg_attr(feature = "serde", derive(serde::Serialize, serde::Deserialize))]
 pub struct EOFCreateInput {
-    /// Caller of Eof Craate
+    /// Caller of Eof Crate
     pub caller: Address,
     /// New contract address.
     pub created_address: Address,
-    /// Values of ether transfered
+    /// Values of ether transferred
     pub value: U256,
     /// Init eof code that is going to be executed.
     pub eof_init_code: Eof,

crates/primitives/src/bytecode/eof.rs

@@ -117,7 +117,7 @@ pub enum EofDecodeError {
     NonSizes,
     /// Missing size.
     ShortInputForSizes,
-    /// Size cant be zero
+    /// Size can't be zero
     ZeroSize,
     /// Invalid code number.
     TooManyCodeSections,

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 efficent 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 verifing that and evaluation at a given point of a commited polynomial is vaild, in a much more 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 verifing that and evaluation at a given point of a committed polynomial is vaild, in a much more bigger scale, implies that `Data is Available`.
 
 This module houses;