diff --git a/guide/bonus/bitcoin/dojo.md b/guide/bonus/bitcoin/dojo.md
index a6f284cf7..e897bd78b 100644
--- a/guide/bonus/bitcoin/dojo.md
+++ b/guide/bonus/bitcoin/dojo.md
@@ -884,14 +884,14 @@ Connect samourai wallet to your own backend
 ## Extras
 
 ### Rescan public keys using Dojo Maintenance Tool
-If no balance is shown in your samourai wallet, it is neccessary to rescan public keys as they are not tracked by Dojo yet.
+If no balance is shown in your samourai wallet, it is necessary to rescan public keys as they are not tracked by Dojo yet.
 
 * Log into `Dojo API and Maintenance Tool` using Tor browser
 * Move to `xpubs tool`, under `Tools` section
 * In samourai wallet go to `Settings > Wallet`, here you can find your public keys
 * Copy and paste all "zpubs" into `xpub tool` and rescan each public key separately
 
-Samourai wallet uses zpubs by default, however if you use other address format than "bc", it is neccessary to rescan other pubs as well
+Samourai wallet uses zpubs by default, however if you use other address format than "bc", it is necessary to rescan other pubs as well
 
 ### Use Auth47 (Paynym) login for Dojo Maintanence Tool
 
diff --git a/guide/bonus/lightning/balance-of-satoshis.md b/guide/bonus/lightning/balance-of-satoshis.md
index e8ff0f1a7..329efb20c 100644
--- a/guide/bonus/lightning/balance-of-satoshis.md
+++ b/guide/bonus/lightning/balance-of-satoshis.md
@@ -182,7 +182,7 @@ To use Balance of Satoshis, we will use the "bos" user.
 
 Circular rebalancing allows to send satoshis out through one channel (which has too little inbound liquidity) and back through another channel (which has too little outbound liquidity).
 
-A good illustration is provided in Chapter 5 of 'Mastering the Lightning Network' by Antonopoulos *et al.* ([source](https://github.com/lnbook/lnbook/blob/ec806916edd6f4d1b2f9da2fef08684f80acb671/05_node_operations.asciidoc#rebalancing-channels){:target="_blank"}) (Alice (A), is your node, Bob (B) and and Chan (C) are two peers with whom you have an opened channel with):
+A good illustration is provided in Chapter 5 of 'Mastering the Lightning Network' by Antonopoulos *et al.* ([source](https://github.com/lnbook/lnbook/blob/ec806916edd6f4d1b2f9da2fef08684f80acb671/05_node_operations.asciidoc#rebalancing-channels){:target="_blank"}) (Alice (A), is your node, Bob (B) and Chan (C) are two peers with whom you have an opened channel with):
 
 ![circular-rebalancing](../../../images/circular-rebalancing-lnbook.png)
 
diff --git a/resources/UTXOracle.py b/resources/UTXOracle.py
index 7a93472b6..6adf39e87 100644
--- a/resources/UTXOracle.py
+++ b/resources/UTXOracle.py
@@ -333,7 +333,7 @@ def Ask_Node(command):
 ##############################################################################
 
 # In pure math a bell curve can be perfectly smooth. But to make a bell curve
-# from a sample of data, one must specifiy a series of buckets, or bins, and then
+# from a sample of data, one must specify a series of buckets, or bins, and then
 # count how many samples are in each bin. If the bin size is too large, say just one
 # large bin, a bell curve can't appear because it will have only one bar. The bell 
 # curve also doesn't appear if the bin size is too small because then there will 
@@ -510,7 +510,7 @@ def Ask_Node(command):
 # of the curve, and then removing extreme values.
 
 
-#remove ouputs below 10k sat (increased from 1k sat in v6)
+#remove outputs below 10k sat (increased from 1k sat in v6)
 for n in range(0,401):
     output_bell_curve_bin_counts[n]=0