Fix/typos (#21017)

This PR fixes a few typos.

consensus/core/src/metrics.rs

@@ -546,7 +546,7 @@ impl NodeMetrics {
             ).unwrap(),
             block_suspensions: register_int_counter_vec_with_registry!(
                 "block_suspensions",
-                "The number block suspensions. The counter is reported uniquely, so if a block is sent for reprocessing while alreadly suspended then is not double counted",
+                "The number block suspensions. The counter is reported uniquely, so if a block is sent for reprocessing while already suspended then is not double counted",
                 &["authority"],
                 registry,
             ).unwrap(),

crates/sui-bridge/src/encoding.rs

@@ -157,7 +157,7 @@ impl BridgeMessageEncoding for BlocklistCommitteeAction {
         bytes.push(u8::try_from(self.members_to_update.len()).unwrap());
 
         // Add list of updated members
-        // Members are represented as pubkey dervied evm addresses (20 bytes)
+        // Members are represented as pubkey derived evm addresses (20 bytes)
         let members_bytes = self
             .members_to_update
             .iter()

crates/sui-bridge/src/sui_syncer.rs

@@ -89,7 +89,7 @@ where
 
     async fn run_event_listening_task(
         // The module where interested events are defined.
-        // Moudle is always of bridge package 0x9.
+        // Module is always of bridge package 0x9.
         module: Identifier,
         mut cursor: Option<EventID>,
         events_sender: mysten_metrics::metered_channel::Sender<(Identifier, Vec<SuiEvent>)>,

external-crates/move/crates/move-analyzer/trace-debug/README.md

@@ -10,7 +10,7 @@ Currently we support trace-debugging of Move unit tests only. and the following
 - line breakpoints
 - disassembly view (disassembled bytecode view) with support for stepping and setting breakpoints in disassembled bytecode files
 
-Note that support for trace-debugging macros and enums is limited at this point - stepping through macros or code related to enums may result in somewhat unexpected results due to how these constructs are handled internally by the Move execution framework. In particular, variable value tracking may be affected when trace-debugging these constructs. Work is ongoing to improve state-of-the-art - improvement suggestions and bug reports files as issues agains Sui's GitHub [repository](https://github.com/MystenLabs/sui) are greatly appreciated.
+Note that support for trace-debugging macros and enums is limited at this point - stepping through macros or code related to enums may result in somewhat unexpected results due to how these constructs are handled internally by the Move execution framework. In particular, variable value tracking may be affected when trace-debugging these constructs. Work is ongoing to improve state-of-the-art - improvement suggestions and bug reports files as issues against Sui's GitHub [repository](https://github.com/MystenLabs/sui) are greatly appreciated.
 
 # How to Install
 
@@ -44,4 +44,4 @@ sui move test FILTER_STRING --trace-execution
 
 ## Trace-debugging a test
 
-Once traces are generated, open a Move file containing the test you want to trace-debug and execute `Run->Start Debug` command. The first time you execute this command, you will have to choose the debugging configuration for Move files, of which there should be only one available. Then you will have to choose a test to trace-debug if there is more than one test in a file (otherwise a trace-debugging session for a single test will start automatically). You can switch between source (regular) view and the disassembly view (where you can inspect and step through disassembled bytecode for lower-level view for Move code execution) by using **Move: Toggle disassembly view** and **Move: Toggle source view** commands from VSCode's command palette.
+Once traces are generated, open a Move file containing the test you want to trace-debug and execute `Run->Start Debug` command. The first time you execute this command, you will have to choose the debugging configuration for Move files, of which there should be only one available. Then you will have to choose a test to trace-debug if there is more than one test in a file (otherwise a trace-debugging session for a single test will start automatically). You can switch between source (regular) view and the disassembly view (where you can inspect and step through disassembled bytecode for lower-level view for Move code execution) by using **Move: Toggle disassembly view** and **Move: Toggle source view** commands from VSCode's command palette.