chore: consolidate typo fixes from multiple PRs (#17387)

HARDFORK-CHECKLIST.md

@@ -30,7 +30,7 @@
 
 Opstack tries to be as close to the L1 engine API as much as possible. Isthmus (Prague equivalent) introduced the first
 deviation from the L1 engine API with an additional field in the `ExecutionPayload`. For this reason the op engine API
-has it's own server traits `OpEngineApi`.
+has its own server traits `OpEngineApi`.
 Adding a new versioned endpoint requires the same changes as for L1 just for the dedicated OP types.
 
 ### Hardforks

bin/reth-bench/src/bench/mod.rs

@@ -38,7 +38,7 @@ pub enum Subcommands {
     ///
     /// One powerful use case is pairing this command with the `cast block` command, for example:
     ///
-    /// `cast block latest--full --json | reth-bench send-payload --rpc-url localhost:5000
+    /// `cast block latest --full --json | reth-bench send-payload --rpc-url localhost:5000
     /// --jwt-secret $(cat ~/.local/share/reth/mainnet/jwt.hex)`
     SendPayload(send_payload::Command),
 }

crates/net/downloaders/src/bodies/bodies.rs

@@ -230,7 +230,7 @@ where
         self.metrics.buffered_responses.set(self.buffered_responses.len() as f64);
     }
 
-    /// Returns a response if it's first block number matches the next expected.
+    /// Returns a response if its first block number matches the next expected.
     fn try_next_buffered(&mut self) -> Option<Vec<BlockResponse<B>>> {
         if let Some(next) = self.buffered_responses.peek() {
             let expected = self.next_expected_block_number();

crates/node/builder/src/builder/mod.rs

@@ -311,7 +311,7 @@ where
     }
 }
 
-/// A [`NodeBuilder`] with it's launch context already configured.
+/// A [`NodeBuilder`] with its launch context already configured.
 ///
 /// This exposes the same methods as [`NodeBuilder`] but with the launch context already configured,
 /// See [`WithLaunchContext::launch`]

crates/trie/common/src/hashed_state.rs

@@ -340,7 +340,7 @@ impl HashedPostState {
     ///
     /// This effectively clears all the fields in the [`HashedPostStateSorted`].
     ///
-    /// This allows us to re-use the allocated space. This allocates new space for the sorted hashed
+    /// This allows us to reuse the allocated space. This allocates new space for the sorted hashed
     /// post state, like `into_sorted`.
     pub fn drain_into_sorted(&mut self) -> HashedPostStateSorted {
         let mut updated_accounts = Vec::new();

crates/trie/common/src/updates.rs

@@ -123,7 +123,7 @@ impl TrieUpdates {
     ///
     /// This effectively clears all the fields in the [`TrieUpdatesSorted`].
     ///
-    /// This allows us to re-use the allocated space. This allocates new space for the sorted
+    /// This allows us to reuse the allocated space. This allocates new space for the sorted
     /// updates, like `into_sorted`.
     pub fn drain_into_sorted(&mut self) -> TrieUpdatesSorted {
         let mut account_nodes = self.account_nodes.drain().collect::<Vec<_>>();

crates/trie/sparse/src/state.rs

@@ -753,7 +753,7 @@ where
             trace!(target: "trie::sparse", ?address, "Retrieving storage root from account leaf to update account");
             // The account was revealed, either...
             if let Some(value) = self.get_account_value(&address) {
-                // ..it exists and we should take it's current storage root or...
+                // ..it exists and we should take its current storage root or...
                 TrieAccount::decode(&mut &value[..])?.storage_root
             } else {
                 // ...the account is newly created and the storage trie is empty.

docs/vocs/docs/pages/guides/history-expiry.mdx

@@ -34,7 +34,7 @@ If enabled, importing blocks from ERA1 files can be done automatically with no m
 
 #### Enabling the ERA stage
 
-The import from ERA1 files within the pre-merge block range is included in the [reth node](../cli/reth/node) synchronization pipeline. It is disabled by default. To enable it, pass the `--era.enable` flag when running the [`node`](../cli/reth/node) command.
+The import from ERA1 files within the pre-merge block range is included in the [reth node](/cli/reth/node) synchronization pipeline. It is disabled by default. To enable it, pass the `--era.enable` flag when running the [`node`](/cli/reth/node) command.
 
 The benefit of using this option is significant increase in the synchronization speed for the headers and mainly bodies stage of the pipeline within the ERA1 block range. We encourage you to use it! Eventually, it will become enabled by default.
 

docs/vocs/docs/pages/run/ethereum.mdx

@@ -94,7 +94,7 @@ In the meantime, consider setting up [observability](/run/monitoring) to monitor
 
 ## Running without a Consensus Layer
 
-We provide a method for running Reth without a Consensus Layer via the `--debug.tip <HASH>` parameter. If you provide that to your node, it will simulate sending an `engine_forkchoiceUpdated` message _once_ and will trigger syncing to the provided block hash. This is useful for testing and debugging purposes, but in order to have a node that can keep up with the tip you'll need to run a CL alongside it. At the moment we have no plans of including a Consensus Layer implementation in Reth, and we are open to including light clients other methods of syncing like importing Lighthouse as a library.
+We provide a method for running Reth without a Consensus Layer via the `--debug.tip <HASH>` parameter. If you provide that to your node, it will simulate sending an `engine_forkchoiceUpdated` message _once_ and will trigger syncing to the provided block hash. This is useful for testing and debugging purposes, but in order to have a node that can keep up with the tip you'll need to run a CL alongside it. At the moment we have no plans of including a Consensus Layer implementation in Reth, and we are open to including light clients and other methods of syncing like importing Lighthouse as a library.
 
 ## Running with Etherscan as Block Source