diff --git a/bridges/primitives/runtime/src/lib.rs b/bridges/primitives/runtime/src/lib.rs index 659d5c0aac..4277af5e46 100644 --- a/bridges/primitives/runtime/src/lib.rs +++ b/bridges/primitives/runtime/src/lib.rs @@ -148,7 +148,7 @@ impl Size for PreComputedSize { pub enum TransactionEra { /// Transaction is immortal. Immortal, - /// Transaction is valid for given number of blocks, starting from given block. + /// Transaction is valid for a given number of blocks, starting from given block. Mortal(BlockNumber, BlockHash, u32), } diff --git a/bridges/relays/lib-substrate-relay/src/finality_pipeline.rs b/bridges/relays/lib-substrate-relay/src/finality_pipeline.rs index 684aafa023..8595ab2842 100644 --- a/bridges/relays/lib-substrate-relay/src/finality_pipeline.rs +++ b/bridges/relays/lib-substrate-relay/src/finality_pipeline.rs @@ -30,7 +30,7 @@ use std::{fmt::Debug, marker::PhantomData, time::Duration}; /// this timeout is used. /// /// There are no any strict requirements on block time in Substrate. But we assume here that all -/// Substrate-based chains will be designed to produce relatively fast (compared to slowest +/// Substrate-based chains will be designed to produce relatively fast (compared to the slowest /// blockchains) blocks. So 1 hour seems to be a good guess for (even congested) chains to mine /// transaction, or remove it from the pool. pub(crate) const STALL_TIMEOUT: Duration = Duration::from_secs(60 * 60); diff --git a/bridges/relays/lib-substrate-relay/src/messages_source.rs b/bridges/relays/lib-substrate-relay/src/messages_source.rs index d6e92d1e51..4d3332d327 100644 --- a/bridges/relays/lib-substrate-relay/src/messages_source.rs +++ b/bridges/relays/lib-substrate-relay/src/messages_source.rs @@ -299,7 +299,7 @@ fn prepare_dummy_messages_delivery_proof() -> SubstrateMes /// /// This function assumes that the chain that is followed by the `self_client` has /// bridge GRANDPA pallet deployed and it provides `best_finalized_header_id_method_name` -/// runtime API to read best finalized Bridged chain header. +/// runtime API to read the best finalized Bridged chain header. pub async fn read_client_state( self_client: &Client, best_finalized_header_id_method_name: &str, diff --git a/bridges/relays/lib-substrate-relay/src/messages_target.rs b/bridges/relays/lib-substrate-relay/src/messages_target.rs index ddf2282792..8ad41281bf 100644 --- a/bridges/relays/lib-substrate-relay/src/messages_target.rs +++ b/bridges/relays/lib-substrate-relay/src/messages_target.rs @@ -377,7 +377,7 @@ where .unwrap_or_else(|_| SC::Balance::max_value()) } -/// Compute fee multiplier that is used by the chain, given couple of fees for transactions +/// Compute fee multiplier that is used by the chain, given a couple of fees for transactions /// that are only differ in dispatch weights. /// /// This function assumes that standard transaction payment pallet is used by the chain.