chore: fix some typos in comments (#2164)

Signed-off-by: oftenoccur <[email protected]>

blockchain/fullblocktests/generate.go

@@ -608,7 +608,7 @@ func (g *testGenerator) saveTipCoinbaseOut() {
 }
 
 // saveSpendableCoinbaseOuts adds all coinbase outputs from the last block that
-// had its coinbase tx output colleted to the current tip.  This is useful to
+// had its coinbase tx output collected to the current tip.  This is useful to
 // batch the collection of coinbase outputs once the tests reach a stable point
 // so they don't have to manually add them for the right tests which will
 // ultimately end up being the best chain.

blockchain/timesorter.go

@@ -20,7 +20,7 @@ func (s timeSorter) Swap(i, j int) {
 	s[i], s[j] = s[j], s[i]
 }
 
-// Less returns whether the timstamp with index i should sort before the
+// Less returns whether the timestamp with index i should sort before the
 // timestamp with index j.  It is part of the sort.Interface implementation.
 func (s timeSorter) Less(i, j int) bool {
 	return s[i] < s[j]

blockchain/validate.go

@@ -761,7 +761,7 @@ func CheckBlockHeaderContext(header *wire.BlockHeader, prevNode HeaderCtx,
 	return nil
 }
 
-// checkBlockContext peforms several validation checks on the block which depend
+// checkBlockContext performs several validation checks on the block which depend
 // on its position within the block chain.
 //
 // The flags modify the behavior of this function as follows:

btcec/schnorr/musig2/nonces_test.go

@@ -111,7 +111,7 @@ type nonceAggTestCases struct {
 }
 
 // TestMusig2AggregateNoncesTestVectors tests that the musig2 implementation
-// passes the nonce aggregration test vectors for musig2 1.0.
+// passes the nonce aggregation test vectors for musig2 1.0.
 func TestMusig2AggregateNoncesTestVectors(t *testing.T) {
 	t.Parallel()
 

mempool/doc.go

@@ -5,7 +5,7 @@
 /*
 Package mempool provides a policy-enforced pool of unmined bitcoin transactions.
 
-A key responsbility of the bitcoin network is mining user-generated transactions
+A key responsibility of the bitcoin network is mining user-generated transactions
 into blocks.  In order to facilitate this, the mining process relies on having a
 readily-available source of transactions to include in a block that is being
 solved.

txscript/engine.go

@@ -450,7 +450,7 @@ func checkMinimalDataPush(op *opcode, data []byte) error {
 	return nil
 }
 
-// executeOpcode peforms execution on the passed opcode.  It takes into account
+// executeOpcode performs execution on the passed opcode.  It takes into account
 // whether or not it is hidden by conditionals, but some rules still must be
 // tested in this case.
 func (vm *Engine) executeOpcode(op *opcode, data []byte) error {