diff --git a/docs/lnd/debugging_lnd.md b/docs/lnd/debugging_lnd.md
index cdb9f7a4..63dd78cd 100644
--- a/docs/lnd/debugging_lnd.md
+++ b/docs/lnd/debugging_lnd.md
@@ -78,7 +78,7 @@ prefix is overwritten by the `LNWL` subsystem.
 
 Moreover when using the `lncli` command the return value will provide the 
 updated list of all subsystems and their associated logging levels. This makes
-it easy to get an overview of the corrent logging level for the whole system.
+it easy to get an overview of the current logging level for the whole system.
 
 Example:
 
diff --git a/docs/lnd/signing_release_candidate.md b/docs/lnd/signing_release_candidate.md
index 263e170d..2d31ac06 100644
--- a/docs/lnd/signing_release_candidate.md
+++ b/docs/lnd/signing_release_candidate.md
@@ -50,7 +50,7 @@ Tip: Download the official release Manifest file to your local maschine and do:
 `diff lnd-v0.18.3-beta/manifest-v0.18.3-beta.txt ~/Downloads/manifest-v0.18.3-beta.txt`
 (example command for a release candidate called `v0.18.3-beta`)  
 Only if all hashes are identical, should you sign the release.  If the digests
-match, see the example signing comand, assuming your PGP signing key is
+match, see the example signing command, assuming your PGP signing key is
 available on your local device:  
 `gpg --local-user $KEYID  --detach-sig --output manifest-$USERNAME-v0.18.3-beta.sig manifest-v0.18.3-beta.txt`.  
 `USERNAME` being the name in the `[verify-install.sh](../scripts/verify-install.sh)`
diff --git a/docs/pool/batch_execution.md b/docs/pool/batch_execution.md
index aaf239ba..7468bbd2 100644
--- a/docs/pool/batch_execution.md
+++ b/docs/pool/batch_execution.md
@@ -22,7 +22,7 @@ Note that the trader can reject signing the batch for any reason, even when the
 
 ### Batch Publication
 
-When all participating traders have signed their inputs in the Batch Execution Transaction, the auctioneer can sign the final input and broadcast the transaction. This transaction can be large, and serve as the funding transaction for potentially hundres of channels! The participating traders only pay chain fees for their inputs and outputs in the transaction, so everybody is saving substantially on fees compared to individually funding channels. If the trader supports account autorenewal and the account was close to expire, its expiry height will be automatically extended after the batch is sucessfully executed.
+When all participating traders have signed their inputs in the Batch Execution Transaction, the auctioneer can sign the final input and broadcast the transaction. This transaction can be large, and serve as the funding transaction for potentially hundres of channels! The participating traders only pay chain fees for their inputs and outputs in the transaction, so everybody is saving substantially on fees compared to individually funding channels. If the trader supports account autorenewal and the account was close to expire, its expiry height will be automatically extended after the batch is successfully executed.
 
 ## Batched Uniform-Price Clearing
 
diff --git a/docs/pool/sidecar_channels.md b/docs/pool/sidecar_channels.md
index 03d4d63d..9bffa948 100644
--- a/docs/pool/sidecar_channels.md
+++ b/docs/pool/sidecar_channels.md
@@ -69,7 +69,7 @@ needs to work, therefore we show the more involved example here.
 
    The addition of this "auto" mode means that both sides need to only execute
    a single and the rest of the negotiation happens in the background. If the
-   `auto` flag is ommitted, then only the capacity and balance need to be
+   `auto` flag is omitted, then only the capacity and balance need to be
    specified, otherwise, all the other information one presents when submitting
    a full order needs to be specified.