diff --git a/src/wallet/mod.rs b/src/wallet/mod.rs
index d2b1e0c8..299eeb9f 100644
--- a/src/wallet/mod.rs
+++ b/src/wallet/mod.rs
@@ -2380,7 +2380,7 @@ mod test {
             builder
                 .add_foreign_utxo(utxo2.outpoint, psbt_input2, satisfaction_weight)
                 .is_ok(),
-            "shoulld be ok when outpoing does match psbt_input"
+            "shoulld be ok when outpoint does match psbt_input"
         );
     }
 
diff --git a/src/wallet/tx_builder.rs b/src/wallet/tx_builder.rs
index bd9181ee..04f11139 100644
--- a/src/wallet/tx_builder.rs
+++ b/src/wallet/tx_builder.rs
@@ -314,7 +314,7 @@ impl<'a, B, D: BatchDatabase, Cs: CoinSelectionAlgorithm<D>, Ctx: TxBuilderConte
         self.add_utxos(&[outpoint])
     }
 
-    /// Add a foreign UTXO i.e. A UTXO not owned by this wallet.
+    /// Add a foreign UTXO i.e. a UTXO not owned by this wallet.
     ///
     /// At a minimum to add a foreign UTXO we need:
     ///
@@ -325,7 +325,7 @@ impl<'a, B, D: BatchDatabase, Cs: CoinSelectionAlgorithm<D>, Ctx: TxBuilderConte
     /// There are several security concerns about adding foregin UTXOs that application
     /// developers should consider. First, how do you know the value of the input is correct? If a
     /// `non_witness_utxo` is provided in the `psbt_input` then this method implicitly verifies the
-    /// value by checking it against the transaction. If only a `wintess_utxo` is provided then this
+    /// value by checking it against the transaction. If only a `witness_utxo` is provided then this
     /// method doesn't verify the value but just takes it as a given -- it is up to you to check
     /// that whoever sent you the `input_psbt` was not lying!
     ///