consistency: fix docs/comment/script typos
What changed, and why it matters
This commit fixes five spelling mistakes in documentation, code comments, and a script comment. None of the changes alter program behavior or affect security.
No security action needed; this is a cosmetic/documentation cleanup commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff contains only typo corrections in user-facing docs (docs/index.rst), inline code comments (main/ble/ble.c, main/camera.c, main/random.c), and a shell script TODO comment (release/scripts/checkfwsvr.sh). No executable logic, data handling, or cryptographic code was modified.
Changed components
docs/index.rstmain/ble/ble.cmain/camera.cmain/random.crelease/scripts/checkfwsvr.shInspect captured patch +5 / −5
### docs/index.rst
@@ -776,7 +776,7 @@ or:
* 'derivation' is the path from the origin to the given xpub - currently it is only used for the Jade signer, where it is used to verify the passed xpub.
* 'xpub' is the signer xpub, as described by the 'fingerprint' and 'derivation' (validated, in the case of this unit's signer).
* 'path' is a path applied to the xpub, to yield the root signer for this multisig. In most cases this is empty '[]'.
-* Alternatively, the contents of the multisig wallet file as produced by several wallet apps (BluwWallet, Sparrow, Nunchuk etc.) can be passed.
+* Alternatively, the contents of the multisig wallet file as produced by several wallet apps (BlueWallet, Sparrow, Nunchuk etc.) can be passed.
.. _register_multisig_reply:
### main/ble/ble.c
@@ -287,7 +287,7 @@ static void ble_start_advertising(void)
JADE_LOGI("Advertising started, (type %u, nrpa %d) with address:", own_addr_type, isnrpa);
print_addr(addr_val);
- // Refeed entropy - this is called whenever the advertisied address changes - ie.
+ // Refeed entropy - this is called whenever the advertised address changes - ie.
// when BLE enabled, and every minute or so all the time no client is connected.
// Called again when the client disconnects. So frequent (if BLE enabled) but not
// completely predictable ...
### main/camera.c
@@ -535,7 +535,7 @@ void jade_camera_process_images(camera_process_fn_t fn, void* ctx, const bool sh
JADE_ASSERT(fn);
// ctx is optional
- // show_ui indicates whether to show a ui or collect cmaera data 'silently'
+ // show_ui indicates whether to show a ui or collect camera data 'silently'
// text_label is optional
// text_button is optional - indicates we want the user to select the images presented
// (otherwise all images are presented) to the given callback function ctx.fn_process()
### main/random.c
@@ -73,7 +73,7 @@ static uint16_t esp32_get_temperature(void)
}
#endif
-// returns up to 32 bytes of randomness (optional), takes optionallly extra entropy
+// returns up to 32 bytes of randomness (optional), optionally adds extra entropy
static void get_random_internal(uint8_t* bytes_out, const size_t len, const uint8_t* additional, const size_t addlen)
{
JADE_ASSERT(rnd_mutex);
### release/scripts/checkfwsvr.sh
@@ -92,7 +92,7 @@ for hwdir in ${HWDIRS}; do
done
done
-# TODO: find firmware files that are present but not listed in index.jon
+# TODO: find firmware files that are present but not listed in index.json
if [ -f "${MISSING_LOG}" ]; then
echo "ERROR: Missing files:"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.