diff --git a/liana-gui/src/app/state/settings/bitcoind.rs b/liana-gui/src/app/state/settings/bitcoind.rs
index f824efea7..f9890378e 100644
--- a/liana-gui/src/app/state/settings/bitcoind.rs
+++ b/liana-gui/src/app/state/settings/bitcoind.rs
@@ -608,7 +608,7 @@ impl RescanSetting {
                     return Command::none();
                 }
                 self.processing = true;
-                info!("Asking deamon to rescan with timestamp: {}", t);
+                info!("Asking daemon to rescan with timestamp: {}", t);
                 return Command::perform(
                     async move {
                         daemon.start_rescan(t.try_into().expect("t cannot be inferior to 0 otherwise genesis block timestamp is chosen"))
diff --git a/lianad/src/bitcoin/mod.rs b/lianad/src/bitcoin/mod.rs
index c4c328bc5..26e755df8 100644
--- a/lianad/src/bitcoin/mod.rs
+++ b/lianad/src/bitcoin/mod.rs
@@ -591,7 +591,7 @@ impl BitcoinInterface for electrum::Electrum {
     }
 }
 
-// FIXME: do we need to repeat the entire trait implemenation? Isn't there a nicer way?
+// FIXME: do we need to repeat the entire trait implementation? Isn't there a nicer way?
 impl BitcoinInterface for sync::Arc<sync::Mutex<dyn BitcoinInterface + 'static>> {
     fn genesis_block_timestamp(&self) -> u32 {
         self.lock().unwrap().genesis_block_timestamp()
diff --git a/lianad/src/database/mod.rs b/lianad/src/database/mod.rs
index 086939b09..c8f13ca52 100644
--- a/lianad/src/database/mod.rs
+++ b/lianad/src/database/mod.rs
@@ -49,7 +49,7 @@ impl DatabaseInterface for SqliteDb {
     }
 }
 
-// FIXME: do we need to repeat the entire trait implemenation? Isn't there a nicer way?
+// FIXME: do we need to repeat the entire trait implementation? Isn't there a nicer way?
 impl DatabaseInterface for sync::Arc<sync::Mutex<dyn DatabaseInterface>> {
     fn connection(&self) -> Box<dyn DatabaseConnection> {
         self.lock().unwrap().connection()
diff --git a/lianad/src/database/sqlite/mod.rs b/lianad/src/database/sqlite/mod.rs
index 93e49255d..9b10439f3 100644
--- a/lianad/src/database/sqlite/mod.rs
+++ b/lianad/src/database/sqlite/mod.rs
@@ -4,7 +4,7 @@
 //! > Multi-thread. In this mode, SQLite can be safely used by multiple threads provided that
 //! > no single database connection is used simultaneously in two or more threads.
 //!
-//! We leverage SQLite's `unlock_notify` feature to synchronize writes accross connection. More
+//! We leverage SQLite's `unlock_notify` feature to synchronize writes across connection. More
 //! about it at https://sqlite.org/unlock_notify.html.
 
 pub mod schema;
diff --git a/lianad/src/lib.rs b/lianad/src/lib.rs
index 3c28c61cb..7ad1333e5 100644
--- a/lianad/src/lib.rs
+++ b/lianad/src/lib.rs
@@ -842,7 +842,7 @@ mod tests {
         // before checking the bitcoind sync status.
         t.join().unwrap();
 
-        // The datadir is created now, so if we restart it it won't create the wo wallet.
+        // The datadir is created now, so if we restart, it won't create the wo wallet.
         let t = thread::spawn({
             let config = config.clone();
             move || {
diff --git a/tests/test_framework/bitcoind.py b/tests/test_framework/bitcoind.py
index b76995199..5ad24ab70 100644
--- a/tests/test_framework/bitcoind.py
+++ b/tests/test_framework/bitcoind.py
@@ -105,7 +105,7 @@ def stop(self):
 
     # wait_for_mempool can be used to wait for the mempool before generating
     # blocks:
-    # True := wait for at least 1 transation
+    # True := wait for at least 1 transaction
     # int > 0 := wait for at least N transactions
     # 'tx_id' := wait for one transaction id given as a string
     # ['tx_id1', 'tx_id2'] := wait until all of the specified transaction IDs