smoldot 2.0.34 → 2.0.35

package/dist/cjs/internals/local-instance.js

@@ -391,7 +391,7 @@ function startLocalInstance(config, wasmModule, eventCallback) {
                 console.assert(disableJsonRpc || jsonRpcMaxPendingRequests != 0, "invalid jsonRpcMaxPendingRequests value passed to local-instance::addChain");
                 // `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);

package/dist/cjs/public-types.d.ts

@@ -351,7 +351,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`.