fix: multiple typos of different importance (#1019)

bin/tx-prover/src/prover.rs

@@ -39,7 +39,7 @@ impl RemoteTransactionProver {
     }
 
     /// Establishes a connection to the remote transaction prover server. The connection is
-    /// mantained for the lifetime of the prover. If the connection is already established, this
+    /// maintained for the lifetime of the prover. If the connection is already established, this
     /// method does nothing.
     async fn connect(&self) -> Result<(), RemoteTransactionProverError> {
         let mut client = self.client.write();

bin/tx-prover/src/proxy/mod.rs

@@ -103,9 +103,9 @@ pub struct TriesCounter {
 /// - Next, the [Self::upstream_peer()] method is called. We use it to figure out which worker will
 ///   process the request. Inside `upstream_peer()`, we pick a worker in a round-robin fashion and
 ///   add the request to the queue of requests for that worker. Once the request gets to the front
-///   of the queue, we forward it to the worker. This step is also in charge of assinging the
+///   of the queue, we forward it to the worker. This step is also in charge of assigning the
 ///   timeouts and enabling HTTP/2. Finally, we establish a connection with the worker.
-/// - Before sending the request to the upstream server and if the connection succeed, the
+/// - Before sending the request to the upstream server and if the connection succeeds, the
 ///   [Self::upstream_request_filter()] method is called. In this method, we ensure that the correct
 ///   headers are forwarded for gRPC requests.
 /// - If the connection fails, the [Self::fail_to_connect()] method is called. In this method, we

miden-lib/asm/kernels/transaction/api.masm

@@ -609,7 +609,7 @@ end
 #! - note_type is the note storage type.
 #! - execution_hint is the note execution hint tag and payload.
 #! - RECIPIENT is the recipient of the note.
-#! - note_idx is the index of the crated note.
+#! - note_idx is the index of the created note.
 #!
 #! Panics if:
 #! - the procedure is called from a non-account context.
@@ -632,7 +632,7 @@ end
 #! Outputs: [note_idx, ASSET, pad(11)]
 #!
 #! Where:
-#! - note_idx is the index of the the note to which the asset is added.
+#! - note_idx is the index of the note to which the asset is added.
 #! - ASSET can be a fungible or non-fungible asset.
 #!
 #! Panics if:

miden-tx/README.md

@@ -6,7 +6,7 @@ This crate contains tool for creating, executing, and proving Miden rollup trans
 
 This crate exposes a few components to compile, run, and prove transactions.
 
-The first requirement is to have a `DataStore` implementation. `DataStore` objects are responsible to load the data needed by the transactions executor, specially the account's code, the reference block data, and the note's inputs.
+The first requirement is to have a `DataStore` implementation. `DataStore` objects are responsible to load the data needed by the transactions executor, especially the account's code, the reference block data, and the note's inputs.
 
 ```rust
 let store = DataStore:new();

miden-tx/src/auth/signatures/mod.rs

@@ -34,7 +34,7 @@ pub fn get_falcon_signature<R: Rng>(
     let nonce = sig.nonce();
     // We convert the signature to a polynomial
     let s2 = sig.sig_poly();
-    // We also need in the VM the expanded key corresponding to the public key the was provided
+    // We also need in the VM the expanded key corresponding to the public key that was provided
     // via the operand stack
     let h = key.compute_pub_key_poly().0;
     // Lastly, for the probabilistic product routine that is part of the verification procedure,