chore: fix some typos

lib/src/network/service.rs

@@ -62,7 +62,7 @@
 //! Once a connection has been established (which is indicated by a [`Event::HandshakeFinished`]
 //! event), one can open a gossip link to this peer using [`ChainNetwork::gossip_open`].
 //!
-//! In order to faciliate this process, the [`ChainNetwork`] provides a "desired gossip links"
+//! In order to facilitate this process, the [`ChainNetwork`] provides a "desired gossip links"
 //! system. Use [`ChainNetwork::gossip_insert_desired`] and [`ChainNetwork::gossip_remove_desired`]
 //! to insert or remove `(ChainId, PeerId, GossipKind)` tuples into the state machine. You can
 //! then use [`ChainNetwork::unconnected_desired`] to obtain a list of [`PeerId`]s that are marked

lib/src/verify/babe.rs

@@ -350,7 +350,7 @@ pub fn verify_header(config: VerifyConfig) -> Result<VerifySuccess, VerifyError>
         // we have checked that the parent's slot number is superior or equal to the epoch
         // start slot number, and we have checked that the epoch cannot transition if the
         // slot number of the block is inferior to the next epoch start. Consequently, the
-        // substraction below cannot underflow.
+        // subtraction below cannot underflow.
         (slot_number - epoch_start_slot) / config.slots_per_epoch // `slots_per_epoch` is a `NonZero` type
     } else {
         0

light-base/src/lib.rs

@@ -598,7 +598,7 @@ impl<TPlat: platform::PlatformRef, TChain> Client<TPlat, TChain> {
         // consumed below.
         let chain_spec_chain_id = chain_spec.id().to_owned();
 
-        // The key generated here uniquely identifies this chain within smoldot. Mutiple chains
+        // The key generated here uniquely identifies this chain within smoldot. Multiple chains
         // having the same key will use the same services.
         //
         // This struct is extremely important from a security perspective. We want multiple

wasm-node/javascript/src/internals/local-instance.ts

@@ -542,7 +542,7 @@ export async function startLocalInstance(config: Config, wasmModule: WebAssembly
 
             // `add_chain` unconditionally allocates a chain id. If an error occurs, however, this chain
             // id will refer to an *erroneous* chain. `chain_is_ok` is used below to determine whether it
-            // has succeeeded or not.
+            // has succeeded or not.
             state.bufferIndices[0] = new TextEncoder().encode(chainSpec)
             state.bufferIndices[1] = new TextEncoder().encode(databaseContent)
             const potentialRelayChainsEncoded = new Uint8Array(potentialRelayChains.length * 4)

wasm-node/javascript/src/public-types.ts

@@ -406,7 +406,7 @@ export interface AddChainOptions {
      * inspecting the chain specification of that parachain (i.e. the `chainSpec` field).
      *
      * This poses a problem in situations where the same client is shared between multiple different
-     * applications: multiple applications could add mutiple different chains with the same `id`,
+     * applications: multiple applications could add multiple different chains with the same `id`,
      * creating an ambiguity, or an application could register malicious chains with small variations
      * of a popular chain's `id` and try to benefit from a typo in a legitimate application's
      * `relayChain`.