What changed, and why it matters
This commit fixes three trivial typos in documentation and a code comment: 'do it it' becomes 'do if it', 'in in' becomes 'in', and 'the the' becomes 'the'. There are no code behavior changes and no security relevance.
No security action needed. Treat as a normal documentation/comment cleanup commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is purely cosmetic. Two changes are in markdown documentation files (doc/lightning-cli.1.md and plugins/bkpr/README.md), and one is in a C header comment (plugins/renepay/mcf.h). No executable code, logic, or data handling is modified.
Changed components
doc/lightning-cli.1.mdplugins/bkpr/README.mdplugins/renepay/mcf.hInspect captured patch +3 / −3
diff --git a/doc/lightning-cli.1.md b/doc/lightning-cli.1.md
index 03f8afaa..e35d255d 100644
--- a/doc/lightning-cli.1.md
+++ b/doc/lightning-cli.1.md
@@ -92,7 +92,7 @@ be changed using `-F`, `-R`, `-J`, `-H` etc.
in a `commando` command to be sent to the connected peer with id
`peerid`, using rune `rune`. This also means that any `--filter` is
handed via commando to the remote peer to reduce its output (which it
-will do it it is v23.02 or newer), rather than trying to do so
+will do if it is v23.02 or newer), rather than trying to do so
locally. Note that currently `-N` is not supported by commando.
COMMANDS
diff --git a/plugins/bkpr/README.md b/plugins/bkpr/README.md
index 658d09f0..8b494cfb 100644
--- a/plugins/bkpr/README.md
+++ b/plugins/bkpr/README.md
@@ -43,7 +43,7 @@ As a plugin writer, if you want to emit onchain events that the bookkeeper shoul
## Withdrawing money (sending to a external account)
-Sending money to an external account is a bit unintuitive in in the UTXO model that we're using to track coin moves; technically a send to an external account is a "deposit" to 3rd party's UTXO.
+Sending money to an external account is a bit unintuitive in the UTXO model that we're using to track coin moves; technically a send to an external account is a "deposit" to 3rd party's UTXO.
To account for these, `bookkeeper` expects to receive a `utxo_deposit` event for the creation of an output to a 3rd party. It's assumed that you'll issue these at transaction creation time, and that they won't be final until we receive notice of spend of the inputs in the tx that created them.
diff --git a/plugins/renepay/mcf.h b/plugins/renepay/mcf.h
index 88f368ce..fe3e7870 100644
--- a/plugins/renepay/mcf.h
+++ b/plugins/renepay/mcf.h
@@ -12,7 +12,7 @@ enum {
// No feasible flow found, either there is not enough known liquidity (or capacity)
// in the channels to complete the payment
RENEPAY_ERR_NOFEASIBLEFLOW,
- // There is at least one feasible flow, but the the cheapest solution that we
+ // There is at least one feasible flow, but the cheapest solution that we
// found is too expensive, we return the result anyways.
RENEPAY_ERR_NOCHEAPFLOW
};
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.