chore: fix some typos in comment (#12671)

This PR focuses on correcting typos and improving clarity in
documentation files.

Thank you very much.

core/store/src/metadata.rs

@@ -56,7 +56,7 @@ pub(super) struct DbMetadata {
 
 impl DbMetadata {
     /// Reads metadata from the database. This method enforces the invariant
-    /// that version and kind must alwasy be set.
+    /// that version and kind must always be set.
     ///
     /// If the database version is not present, returns an error.  Similarly, if
     /// database version is ≥ [`DB_VERSION_WITH_KIND`] but the kind is not

docs/practices/workflows/benchmarking_synthetic_workloads.md

@@ -11,7 +11,7 @@ This approach has the following benefits:
 
 The main drawbacks of synthetic benchmarks are:
 
-- Drawing conclusions is limited as real world traffic is not homogenous.
+- Drawing conclusions is limited as real world traffic is not homogeneous.
 - Calibrating traffic generation parameters can be cumbersome.
 
 The tooling for synthetic benchmarks is available in [`benchmarks/bm-synth`](../../../benchmarks/bm-synth).

integration-tests/src/test_loop/utils/trie_sanity.rs

@@ -118,7 +118,7 @@ impl TrieSanityCheck {
         check_shard_uids
     }
 
-    // Check trie sanity and keep track of which shards were succesfully fully checked
+    // Check trie sanity and keep track of which shards were successfully fully checked
     pub fn assert_state_sanity(&mut self, clients: &[&Client], new_num_shards: NumShards) {
         for client in clients {
             let signer = client.validator_signer.get();

integration-tests/src/tests/runtime/test_yield_resume.rs

@@ -162,7 +162,7 @@ fn resume_without_yield() {
         )
         .unwrap();
 
-    // expect the execution to suceed, but return 'false'
+    // expect the execution to succeed, but return 'false'
     assert_eq!(
         res.status,
         FinalExecutionStatus::SuccessValue(vec![0u8]),

pytest/tests/replay/README.md

@@ -15,7 +15,7 @@ Prerequisites:
 
 In order to set up and launch replay, we take the following steps:
 
-Make sure you have the right enviroment variables:
+Make sure you have the right environment variables:
 ```shell
 export PYTHONPATH=./pytest/lib
 ```

pytest/tests/sanity/split_storage.py

@@ -125,7 +125,7 @@ def step2_archival_node_sync_test(self):
         logger.info(f"Starting the archival <- split storage sync test")
 
         # Archival nodes do not run state sync. This means that if peers
-        # ran away further than epoch_lenght * gc_epoch_num, archival nodes
+        # ran away further than epoch_length * gc_epoch_num, archival nodes
         # will not be able to further sync. In practice it means we need a long
         # enough epoch_length or more gc_epoch_num to keep.
         epoch_length = 10