diff --git a/lnwire/commit_signature.go b/lnwire/commit_signature.go
index 5747b363..42902de2 100644
--- a/lnwire/commit_signature.go
+++ b/lnwire/commit_signature.go
@@ -10,8 +10,8 @@ import (
 )
 
 // CommitSignature is sent by either side to stage any pending HTLC's in the
-// reciever's pending set which has not explcitly been rejected via an
-// HTLCAddReject message. Implictly, the new commitment transaction constructed
+// receiver's pending set which has not explicitly been rejected via an
+// HTLCAddReject message. Implicitly, the new commitment transaction constructed
 // which has been signed by CommitSig includes all HTLC's in the remote node's
 // pending set. A CommitSignature message may be sent after a series of HTLCAdd
 // messages in order to batch add several HTLC's with a single signature
@@ -21,7 +21,7 @@ type CommitSignature struct {
 	// CommitSignature applies to.
 	ChannelPoint *wire.OutPoint
 
-	// LogIndex is the index into the reciever's HTLC log to which this
+	// LogIndex is the index into the receiver's HTLC log to which this
 	// commitment signature covers. In order to properly verify this
 	// signature, the receiver should include all the HTLC's within their
 	// log with an index less-than-or-equal to the listed log-index.
@@ -35,7 +35,7 @@ type CommitSignature struct {
 	// CommitSig is Alice's signature for Bob's new commitment transaction.
 	// Alice is able to send this signature without requesting any additional
 	// data due to the piggybacking of Bob's next revocation hash in his
-	// prior CommitRevocation message, as well as the cannonical ordering
+	// prior CommitRevocation message, as well as the canonical ordering
 	// used for all inputs/outputs within commitment transactions.
 	CommitSig *btcec.Signature
 }
diff --git a/peer.go b/peer.go
index 2c6a0d05..28a01589 100644
--- a/peer.go
+++ b/peer.go
@@ -980,7 +980,7 @@ out:
 			// update in some time, check to see if we have any
 			// pending updates we need to commit. If so, then send
 			// an update incrementing the unacked counter is
-			// succesful.
+			// successfully.
 			if !state.channel.PendingUpdates() &&
 				len(state.htlcsToSettle) == 0 {
 				continue
@@ -1221,7 +1221,7 @@ func (p *peer) handleUpstreamMsg(state *commitmentState, msg lnwire.Message) {
 
 		// If any of the htlc's eligible for forwarding are pending
 		// settling or timeing out previous outgoing payments, then we
-		// can them from the pending set, and signal the requster (if
+		// can them from the pending set, and signal the requester (if
 		// existing) that the payment has been fully fulfilled.
 		var bandwidthUpdate btcutil.Amount
 		settledPayments := make(map[lnwallet.PaymentHash]struct{})