chore(github): use codespell to inspect and correct spelling issues (#7775)

Signed-off-by: jsvisa <delweng@gmail.com>
Co-authored-by: Matthias Seitz <matthias.seitz@outlook.de>

crates/rpc/rpc-api/src/engine.rs

@@ -131,7 +131,7 @@ pub trait EngineApi<Engine: EngineTypes> {
     /// layer p2p specification, meaning the input should be treated as untrusted or potentially
     /// adversarial.
     ///
-    /// Implementors should take care when acting on the input to this method, specifically
+    /// Implementers should take care when acting on the input to this method, specifically
     /// ensuring that the range is limited properly, and that the range boundaries are computed
     /// correctly and without panics.
     #[method(name = "getPayloadBodiesByRangeV1")]

crates/rpc/rpc-api/src/ganache.rs

@@ -34,7 +34,7 @@ pub trait GanacheApi {
     /// is the snapshot id to revert to. This deletes the given snapshot, as well as any snapshots
     /// taken after (e.g.: reverting to id 0x1 will delete snapshots with ids 0x1, 0x2, etc.).
     ///
-    /// Reutnrs `true` if a snapshot was reverted, otherwise `false`.
+    /// Returns `true` if a snapshot was reverted, otherwise `false`.
     #[method(name = "revert")]
     async fn evm_revert(&self, snapshot_id: U256) -> RpcResult<bool>;
 

crates/rpc/rpc-builder/src/lib.rs

@@ -717,7 +717,7 @@ impl RpcModuleSelection {
 
     /// Creates a new [RpcModule] based on the configured reth modules.
     ///
-    /// Note: This will always create new instance of the module handlers and is therefor only
+    /// Note: This will always create new instance of the module handlers and is therefore only
     /// recommended for launching standalone transports. If multiple transports need to be
     /// configured it's recommended to use the [RpcModuleBuilder].
     #[allow(clippy::too_many_arguments)]

crates/rpc/rpc-engine-api/src/engine_api.rs

@@ -292,7 +292,7 @@ where
     /// layer p2p specification, meaning the input should be treated as untrusted or potentially
     /// adversarial.
     ///
-    /// Implementors should take care when acting on the input to this method, specifically
+    /// Implementers should take care when acting on the input to this method, specifically
     /// ensuring that the range is limited properly, and that the range boundaries are computed
     /// correctly and without panics.
     pub async fn get_payload_bodies_by_range(
@@ -661,7 +661,7 @@ where
     /// layer p2p specification, meaning the input should be treated as untrusted or potentially
     /// adversarial.
     ///
-    /// Implementors should take care when acting on the input to this method, specifically
+    /// Implementers should take care when acting on the input to this method, specifically
     /// ensuring that the range is limited properly, and that the range boundaries are computed
     /// correctly and without panics.
     ///

crates/rpc/rpc/src/eth/signer.rs

@@ -53,7 +53,7 @@ impl DevSigner {
     /// Generates a random dev signer which satisfies [EthSigner] trait
     pub(crate) fn random() -> Box<dyn EthSigner> {
         let mut signers = Self::random_signers(1);
-        signers.pop().expect("expect to generate at leas one signer")
+        signers.pop().expect("expect to generate at least one signer")
     }
 
     /// Generates provided number of random dev signers

crates/rpc/rpc/src/lib.rs

@@ -12,7 +12,7 @@
 //!
 //! To avoid this, all blocking or CPU intensive handlers must be spawned to a separate task. See
 //! the [EthApi] handler implementations for examples. The rpc-api traits make no use of the
-//! available jsonrpsee `blocking` attribute to give implementors more freedom because the
+//! available jsonrpsee `blocking` attribute to give implementers more freedom because the
 //! `blocking` attribute and async handlers are mutually exclusive. However, as mentioned above, a
 //! lot of handlers make use of async functions, caching for example, but are also using blocking
 //! disk-io, hence these calls are spawned as futures to a blocking task manually.