chore: fix some comments

README_offline_transaction_signing.md

@@ -523,15 +523,15 @@ shortfalls:
  - AMOUNT - How many coins you want to send. You can specify payments not only up
  to 2 decimal places, traditionally reserved for cents, but up to 6 
  decimal places. You can therefore send milli (0.001) and micro (0.000001)
- coin payments. In the transaction text is is written as value.fraction,
+ coin payments. In the transaction text is written as value.fraction,
  i.e. 12.4 or 0.0024
  - MEMO - The text memo is a description that you and the recipient can read 
  regarding the transaction. It can for instance contain an invoice 
  number for goods purchased.
  - CONFIRMATIONS - How many network confirmations must occur before the transaction
  is deemed successful. It is safe to leave this at 1
  - FEE - How many coins you want to pay the pirate network backoffice in fees
- for maintaining the pirate network. In the transaction text is is 
+ for maintaining the pirate network. In the transaction text is 
  written as value.fraction, i.e. 0.0001
 
  It's best to construct the transaction in an external text editor and copy and

src/cc/hempcoin_notes.txt

@@ -53,7 +53,7 @@ paymentsfund:
 get the payment fund scriptpubkey hex from vout 0: (the split it at OP_CHECKCRYPTOCONDITION or 'cc' )
  2ea22c8020987fad30df055db6fd922c3a57e55d76601229ed3da3b31340112e773df3d0d28103120c008203000401cc 2a0401f00101246a22f046337db779358deaa69b9af053e27d85cb8e8e48b0b13805c084b04f87be6577ee75
 
- put the second half into an OP_RETURN: (the remaining part of the the above scriptpubkey) eg.
+ put the second half into an OP_RETURN: (the remaining part of the above scriptpubkey) eg.
  ./komodo-cli -ac_name=TESTHC opreturn_burn 1 2a0401f00101246a22f046337db779358deaa69b9af053e27d85cb8e8e48b0b13805c084b04f87be6577ee75
  opret_burn takes any burn amount and arbitrary hex string. (RPC works, but may have bugs, likely use this for LABS too with some fixes)
  this gives a raw hex. Decode it and check the OP_RETURN is right before sending. 

src/cc/sudoku.cpp

@@ -149,7 +149,7 @@
 /* And that brings me to this topic: What do all these points mean? */
 /* */
 /* Well, who knows? This is still subjective, and the weighting system I've chosen */
-/* for point scoring is is largely arbitrary. But based upon feedback from a number */
+/* for point scoring is largely arbitrary. But based upon feedback from a number */
 /* of individuals, a rough scale of difficulty plays out as follows: */
 /* */
 /* DEGREE OF DIFFICULTY | SCORE */

src/secp256k1/src/modules/musig/example.c

@@ -104,7 +104,7 @@ int sign(const secp256k1_context* ctx, unsigned char seckeys[][32], const secp25
  for (i = 0; i < N_SIGNERS; i++) {
  for (j = 0; j < N_SIGNERS; j++) {
  /* To check whether signing was successful, it suffices to either verify
- * the the combined signature with the combined public key using
+ * the combined signature with the combined public key using
  * secp256k1_schnorrsig_verify, or verify all partial signatures of all
  * signers individually. Verifying the combined signature is cheaper but
  * verifying the individual partial signatures has the advantage that it