chore: remove repetitive words (#6219)

Signed-off-by: careworry <[email protected]>

beacon_chain/gossip_processing/block_processor.nim

@@ -525,7 +525,7 @@ proc storeBlock(
  # has been finalized - this speeds up forward sync - in the worst case
  # that the claim is false, we will correct every time we process a block
  # from an honest source (or when we're close to head).
- # Occasionally we also send a payload to the the EL so that it can
+ # Occasionally we also send a payload to the EL so that it can
  # progress in its own sync.
  NewPayloadStatus.noResponse
  else:

beacon_chain/spec/digest.nim

@@ -12,7 +12,7 @@
 # https://github.com/ethereum/consensus-specs/blob/v1.4.0/specs/phase0/beacon-chain.md#hash
 #
 # In Phase 0 the beacon chain is deployed with SHA256 (SHA2-256).
-# Note that is is different from Keccak256 (often mistakenly called SHA3-256)
+# Note that is different from Keccak256 (often mistakenly called SHA3-256)
 # and SHA3-256.
 #
 # In execution, the default hash function is Keccak256,

beacon_chain/spec/state_transition.nim

@@ -328,7 +328,7 @@ proc state_transition*(
  ## given state must be of a lower slot, or, in case the `slotProcessed` flag
  ## is set, can be the slot state of the same slot as the block (where the
  ## slot state is the state without any block applied). To create a slot state,
- ## advance the state corresponding to the the parent block using
+ ## advance the state corresponding to the parent block using
  ## `process_slots`.
  ##
  ## To run the state transition function in preparation for block production,

beacon_chain/validator_client/block_service.nim

@@ -878,7 +878,7 @@ proc runBlockEventMonitor(service: BlockServiceRef,
  plain = RestPlainResponse(status: resp.status,
  contentType: resp.contentType, data: body)
  reason = plain.getErrorMessage()
- debug "Unable to to obtain events stream", code = resp.status,
+ debug "Unable to obtain events stream", code = resp.status,
  reason = reason
  Opt.none(HttpClientResponseRef)
  except RestError as exc:

docs/e2store.md

@@ -309,7 +309,7 @@ The state stores the block root of the latest `SLOTS_PER_HISTORICAL_ROOT` blocks
 
 ## Why include the state at all?
 
-This is a tradeoff between being able to access state data such as validator keys and balances directly vs and recreating it by applying each block one by one from from genesis. Given an era file, it is possible to start processing the chain from there onwards.
+This is a tradeoff between being able to access state data such as validator keys and balances directly vs and recreating it by applying each block one by one from genesis. Given an era file, it is possible to start processing the chain from there onwards.
 
 ## Why the weird file name?
 

tests/consensus_spec/test_fixture_sanity_blocks.nim

@@ -48,7 +48,7 @@ proc runTest(
 
  if hasPostState:
  # The return value is the block rewards, which aren't tested here;
- # the .expect() already handles the the validaty check.
+ # the .expect() already handles the validaty check.
  discard state_transition(
  defaultRuntimeConfig, fhPreState[], blck, cache, info, flags = {},
  noRollback).expect("should apply block")

tests/consensus_spec/test_fixture_transition.nim

@@ -61,7 +61,7 @@ proc runTest(
  flags = {skipStateRootValidation}, noRollback)
 
  # The return value is the block rewards, which aren't tested here;
- # the .expect() already handles the the validaty check.
+ # the .expect() already handles the validaty check.
  discard res.expect("no failure when applying block " & $i)
  else:
  let
@@ -72,7 +72,7 @@ proc runTest(
  flags = {skipStateRootValidation}, noRollback)
 
  # The return value is the block rewards, which aren't tested here;
- # the .expect() already handles the the validaty check.
+ # the .expect() already handles the validaty check.
  discard res.expect("no failure when applying block " & $i)
 
  let postState = newClone(