What the developer wrote
Authored by Ilya Artemov
Typo fixes
What changed, and why it matters
This commit fixes two spelling mistakes: one in the changelog ('jome' to 'home') and one in a code comment ('In te case' to 'In the case'). No program logic, security behavior, or functionality was changed.
No security action needed; this is a documentation/comment-only cleanup.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff is purely cosmetic. CHANGELOG.md receives a typo correction in a release note sentence. src/crypto.c receives a typo correction inside a comment explaining BIP32 path handling. No executable code, buffer sizes, cryptographic operations, control flow, or data handling were modified.
Changed components
Inspect captured patch +2 / −2
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8bea297..d9597a3 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -13,7 +13,7 @@ Dates are in `dd-mm-yyyy` format.
- for `bitcoin_recovery`
- `HAVE_APPLICATION_FLAG_DERIVE_MASTER` enabled so fully non-hardened paths can be used
- - A warning dispalyed on jome screen
+ - A warning dispalyed on home screen
### Fixed
diff --git a/src/crypto.c b/src/crypto.c
index f91f7f7..fcca770 100644
--- a/src/crypto.c
+++ b/src/crypto.c
@@ -329,7 +329,7 @@ cx_err_t get_extended_pubkey_at_path(const uint32_t bip32_path[],
if (bip32_path_len > 0) {
if (bip32_path_len == 1) {
- // In te case of L1 path the parent is the master key so we use special function
+ // In the case of L1 path the parent is the master key so we use special function
parent_fingerprint = crypto_get_master_key_fingerprint();
} else {
uint8_t parent_pubkey[33];
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.