chore: fix some typos (#4095)

bridges/relays/messages/src/message_race_delivery.rs

@@ -446,7 +446,7 @@ where
 		))
 	}
 
-	/// Returns lastest confirmed message at source chain, given source block.
+	/// Returns latest confirmed message at source chain, given source block.
 	fn latest_confirmed_nonce_at_source(&self, at: &SourceHeaderIdOf<P>) -> Option<MessageNonce> {
 		self.latest_confirmed_nonces_at_source
 			.iter()

bridges/relays/messages/src/message_race_strategy.rs

@@ -567,7 +567,7 @@ mod tests {
 		let source_header_1 = header_id(1);
 		let target_header_1 = header_id(1);
 
-		// we start in perfec sync state - all headers are synced and finalized on both ends
+		// we start in perfect sync state - all headers are synced and finalized on both ends
 		let mut state = TestRaceStateImpl {
 			best_finalized_source_header_id_at_source: Some(source_header_1),
 			best_finalized_source_header_id_at_best_target: Some(source_header_1),

bridges/relays/parachains/README.md

@@ -23,7 +23,7 @@ to return the best known head of given parachain. When required, it must be able
 finality delivery transaction to the target node.
 
 The main entrypoint for the crate is the [`run` function](./src/parachains_loop.rs), which takes source and target
-clients and [`ParachainSyncParams`](./src/parachains_loop.rs) parameters. The most imporant parameter is the
+clients and [`ParachainSyncParams`](./src/parachains_loop.rs) parameters. The most important parameter is the
 `parachains` - it is the set of parachains, which relay tracks and updates. The other important parameter that
 may affect the relay operational costs is the `strategy`. If it is set to `Any`, then the finality delivery
 transaction is submitted if at least one of tracked parachain heads is updated. The other option is `All`. Then