tools: I cannot spell recurrEnce.
What changed, and why it matters
This commit adds a spelling check to the project's tooling. It prevents developers from misspelling the word 'recurrence' as 'recurrance' in the codebase. There is no security relevance.
No security action required. Treat as a normal code-quality/linting improvement.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The patch extends tools/check-spelling.sh with an additional grep-based check that fails CI if the misspelling ‘recurrance’ appears anywhere in the repository. It is a pure code-quality/linting change with no functional, cryptographic, or network security impact.
Changed components
tools/check-spelling.shInspect captured patch +5 / −0
diff --git a/tools/check-spelling.sh b/tools/check-spelling.sh
index 6fce914a..c106b614 100755
--- a/tools/check-spelling.sh
+++ b/tools/check-spelling.sh
@@ -10,3 +10,8 @@ if git --no-pager grep -nHiEP '(?<!en|htl)ctlv' -- . ':!tools/check-spelling.sh'
echo "It's check lock time verify, not check time lock verify!" >&2
exit 1
fi
+
+if git --no-pager grep -nHiEP 'recurrance' -- . ':!tools/check-spelling.sh'; then
+ echo "It's recurrEnce not recurrAnce!" >&2
+ exit 1
+fi
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.