chore: remove redundant words in comment (#1759)

remove redundant words in comment
cardano-scaling · Dec 30, 2024 · 11a8d79 · 11a8d79
2 parents 1b447f3 + 0eb4637
commit 11a8d79
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/hydra-cardano-api/src/Hydra/Cardano/Api/TxIn.hs b/hydra-cardano-api/src/Hydra/Cardano/Api/TxIn.hs
@@ -55,7 +55,7 @@ fromPlutusTxOutRef (Plutus.TxOutRef (Plutus.TxId bytes) ix) =
 -- | Convert a cardano-api 'TxIn' into a plutus 'TxOutRef'.
 toPlutusTxOutRef :: TxIn -> Plutus.TxOutRef
 toPlutusTxOutRef txIn =
-  -- XXX: The upstream 'transTxIn' works only with the the PlutusV1 type, so we
+  -- XXX: The upstream 'transTxIn' works only with the PlutusV1 type, so we
   -- needed to vendor its definition here.
   let (Ledger.TxIn (Ledger.TxId safe) txIx) = toLedgerTxIn txIn
    in Plutus.TxOutRef (Plutus.TxId $ transSafeHash safe) (toInteger $ Ledger.txIxToInt txIx)

diff --git a/hydra-node/src/Hydra/Chain/CardanoClient.hs b/hydra-node/src/Hydra/Chain/CardanoClient.hs
@@ -34,7 +34,7 @@ instance Exception QueryException where
   displayException = \case
     QueryAcquireException failure -> show failure
     QueryEraMismatchException EraMismatch{ledgerEraName, otherEraName} ->
-      -- NOTE: The "ledger" here is the the one in the cardano-node and "otherEra" is the one we picked for the query.
+      -- NOTE: The "ledger" here is the one in the cardano-node and "otherEra" is the one we picked for the query.
       printf "Connected to cardano-node in unsupported era %s, while we requested %s. Please upgrade your hydra-node." ledgerEraName otherEraName
     QueryProtocolParamsConversionException err -> show err
     QueryProtocolParamsEraNotSupported unsupportedEraName ->

diff --git a/hydra-node/test/Hydra/HeadLogicSpec.hs b/hydra-node/test/Hydra/HeadLogicSpec.hs
@@ -2,7 +2,7 @@
 {-# OPTIONS_GHC -Wno-ambiguous-fields #-}
 {-# OPTIONS_GHC -Wno-unused-do-bind #-}
 
--- | Unit tests of the the protocol logic in 'HeadLogic'. These are very fine
+-- | Unit tests of the protocol logic in 'HeadLogic'. These are very fine
 -- grained and specific to individual steps in the protocol. More high-level of
 -- the protocol logic, especially between multiple parties can be found in
 -- 'Hydra.BehaviorSpec'.