Fix: typos (#1727)

Author: GoodDaisy

Diff for: zkevm-circuits/src/evm_circuit/execution/invalid_tx.rs

@@ -252,7 +252,7 @@ mod test {
             CircuitTestBuilder::new_from_test_ctx(ctx).run();
         }
 
-        // Check diferent permutations to make sure all transitions work correctly
+        // Check different permutations to make sure all transitions work correctly
         test_ok([false]);
         test_ok([true]);
         test_ok([false, false]);

Diff for: zkevm-circuits/src/keccak_circuit.rs

@@ -308,7 +308,7 @@ impl<F: Field> SubCircuitConfig<F> for KeccakCircuitConfig<F> {
         // multiple rows with lookups in a way that doesn't require any
         // extra additional cells or selectors we have to put all `s[i]`'s on the same
         // row. This isn't that strong of a requirement actually because we the
-        // words are split into multipe parts, and so only the parts at the same
+        // words are split into multiple parts, and so only the parts at the same
         // position of those words need to be on the same row.
         let target_word_sizes = target_part_sizes(part_size);
         let num_word_parts = target_word_sizes.len();

Diff for: zkevm-circuits/src/mpt_circuit/rlp_gadgets.rs

@@ -408,7 +408,7 @@ impl<F: Field> RLPValueGadget<F> {
         self.is_long.rot(meta, rot)
     }
 
-    // RLP byte containing the lenght of the length,
+    // RLP byte containing the length of the length,
     // followed by the length, followed by the actual data
     pub(crate) fn is_very_long(&self) -> Expression<F> {
         self.is_very_long.expr()
@@ -507,7 +507,7 @@ impl RLPValueWitness {
         self.is_long
     }
 
-    // RLP byte containing the lenght of the length,
+    // RLP byte containing the length of the length,
     // followed by the length, followed by the actual data
     pub(crate) fn is_very_long(&self) -> bool {
         self.is_very_long
@@ -716,7 +716,7 @@ impl<F: Field> RLPItemGadget<F> {
         })
     }
 
-    // RLP byte containing the lenght of the length,
+    // RLP byte containing the length of the length,
     // followed by the length, followed by the actual data
     pub(crate) fn is_very_long(&self) -> Expression<F> {
         circuit!([meta, _cb!()], {

Diff for: zkevm-circuits/src/super_circuit.rs

@@ -138,7 +138,7 @@ impl<F: Field> SubCircuitConfig<F> for SuperCircuitConfig<F> {
         let u10_table = UXTable::construct(meta);
         let u16_table = UXTable::construct(meta);
 
-        // Use a mock randomness instead of the randomness derived from the challange
+        // Use a mock randomness instead of the randomness derived from the challenge
         // (either from mock or real prover) to help debugging assignments.
         let power_of_randomness: [Expression<F>; 31] =
             array::from_fn(|i| Expression::Constant(mock_randomness.pow([1 + i as u64, 0, 0, 0])));

Diff for: zkevm-circuits/src/test_util.rs

@@ -36,7 +36,7 @@ const NUM_BLINDING_ROWS: usize = 64;
 /// builder pattern provides functions that allow to pass different functions
 /// that the prover should execute when verifying the CTB correctness.
 ///
-/// The CTB also includes a mechanism to recieve calls that will modify the
+/// The CTB also includes a mechanism to receive calls that will modify the
 /// block produced from the [`TestContext`] and apply them before starting to
 /// compute the proof.
 ///

Diff for: zkevm-circuits/src/tx_circuit.rs

@@ -31,7 +31,7 @@ use std::{marker::PhantomData, ops::Deref};
 /// Number of static fields per tx: [nonce, gas, gas_price,
 /// caller_address, callee_address, is_create, value, call_data_length,
 /// call_data_gas_cost, tx_sign_hash].
-/// Note that call data bytes are layed out in the TxTable after all the static
+/// Note that call data bytes are laid out in the TxTable after all the static
 /// fields arranged by txs.
 pub(crate) const TX_LEN: usize = 10;
 

Diff for: zkevm-circuits/src/tx_circuit/sign_verify.rs

@@ -63,7 +63,7 @@ impl<F: Field> SignVerifyChip<F> {
     pub fn new(max_verif: usize) -> Self {
         // TODO: Investigate if it is safe to use a random point as aux generator that
         // is chosen by the prover.  If this is unsafe, we will need to update the
-        // EccChip to calculate an aux generator using the challange API.
+        // EccChip to calculate an aux generator using the challenge API.
         // https://github.com/privacy-scaling-explorations/halo2wrong/issues/53
         let mut rng = ChaCha20Rng::seed_from_u64(0);
         let aux_generator =