chore: remove repeat words

crates/core/src/uint.rs

@@ -472,7 +472,7 @@ impl Uint {
 }
 
 /// The maximum absolute value a [`I256`] may have.
-/// Note the the last digit is 2^63 - 1. We add this cap so
+/// Note the last digit is 2^63 - 1. We add this cap so
 /// we can use two's complement.
 pub const MAX_SIGNED_VALUE: Uint =
     Uint([u64::MAX, u64::MAX, u64::MAX, 9223372036854775807]);

crates/namada/src/vm/wasm/compilation_cache/common.rs

@@ -106,7 +106,7 @@ impl<N: CacheName, A: WasmCacheAccess> Cache<N, A> {
     /// Get a WASM module from LRU cache, from a file or compile it and cache
     /// it. If the cache access is set to [`crate::vm::WasmCacheRwAccess`], it
     /// updates the position in the LRU cache. Otherwise, the compiled
-    /// module will not be be cached, if it's not already.
+    /// module will not be cached, if it's not already.
     pub fn fetch(
         &mut self,
         code_hash: &Hash,

crates/node/src/ethereum_oracle/events.rs

@@ -43,7 +43,7 @@ pub mod eth_events {
 
     impl PendingEvent {
         /// Decodes bytes into an [`EthereumEvent`] based on the signature.
-        /// This is is turned into a [`PendingEvent`] along with the block
+        /// This is turned into a [`PendingEvent`] along with the block
         /// height passed in here.
         ///
         /// If the event contains a confirmations field,

crates/parameters/src/lib.rs

@@ -271,7 +271,7 @@ where
     storage.write(&key, value)
 }
 
-/// Read the the epoch duration parameter from store
+/// Read the epoch duration parameter from store
 pub fn read_epoch_duration_parameter<S>(
     storage: &S,
 ) -> namada_storage::Result<EpochDuration>
@@ -286,7 +286,7 @@ where
         .into_storage_result()
 }
 
-/// Read the the masp epoch multiplier parameter from store
+/// Read the masp epoch multiplier parameter from store
 pub fn read_masp_epoch_multiplier_parameter<S>(
     storage: &S,
 ) -> namada_storage::Result<u64>

crates/proof_of_stake/src/tests/test_validator.rs

@@ -624,7 +624,7 @@ fn test_validator_sets() {
     );
     assert_eq!(tm_updates[1], ValidatorSetUpdate::Deactivated(pk2));
 
-    // Unbond some stake from val1, it should be be swapped with the greatest
+    // Unbond some stake from val1, it should be swapped with the greatest
     // below-capacity validator val2 into the below-capacity set. The stake of
     // val1 will go below 1 NAM, which is the validator_stake_threshold, so it
     // will enter the below-threshold validator set.
@@ -828,7 +828,7 @@ fn test_validator_sets() {
     );
     assert_eq!(tm_updates[1], ValidatorSetUpdate::Deactivated(pk1));
 
-    // Bond some stake to val6, it should be be swapped with the lowest
+    // Bond some stake to val6, it should be swapped with the lowest
     // consensus validator val2 into the consensus set
     let bond = token::Amount::from_uint(500_000, 0).unwrap();
     let stake6 = stake6 + bond;

crates/tests/src/e2e/ledger_tests.rs

@@ -1060,7 +1060,7 @@ where
 /// 4. Run it to get it to double vote and sign blocks
 /// 5. Submit a valid token transfer tx to validator 0
 /// 6. Wait for double signing evidence
-/// 7. Make sure the the first validator can proceed to the next epoch
+/// 7. Make sure the first validator can proceed to the next epoch
 #[test]
 fn double_signing_gets_slashed() -> Result<()> {
     use std::net::SocketAddr;
@@ -1347,7 +1347,7 @@ fn double_signing_gets_slashed() -> Result<()> {
         .exp_regex(r"Validator [a-z0-9]+ is in the .* set")
         .unwrap();
 
-    // 7. Make sure the the first validator can proceed to the next epoch
+    // 7. Make sure the first validator can proceed to the next epoch
     epoch_sleep(&test, &validator_one_rpc, 120)?;
 
     // Make sure there are no errors

documentation/dev/src/explore/design/ledger/pos-integration.md

@@ -55,7 +55,7 @@ All the fees that are charged in a transaction execution (DKG transaction wrappe
 
 The transactions are assumed to be applied in epoch `n`. Any transaction that modifies [epoched data](https://specs.namada.net/economics/proof-of-stake/bonding-mechanism.html#epoched-data) updates the structure as described in [epoched data storage](https://specs.namada.net/economics/proof-of-stake/bonding-mechanism.html#storage).
 
-For slashing tokens, we implement a [PoS slash pool account](vp.md#pos-slash-pool-vp). Slashed tokens should be credited to this account and, for now, no tokens can be be debited by anyone.
+For slashing tokens, we implement a [PoS slash pool account](vp.md#pos-slash-pool-vp). Slashed tokens should be credited to this account and, for now, no tokens can be debited by anyone.
 
 ### Validator transactions