Merge branch 'release-24.03.0' of https://github.com/selfcustody/krux …

…into release-24.03.0

CHANGELOG.md

@@ -1,4 +1,4 @@
-# Changelog 24.03.0 - March 11, 2024
+# Changelog 24.03.0 - March 12, 2024
 
 ## Changes
 
@@ -56,6 +56,9 @@ Use the latest Embit release.
 ### Maix Dock Simulator
 Now Krux PC simulator can also run in Maix Dock mode, mimicking appearance and characteristics of the most DIY Krux device.
 
+### New Compatible Device - Yahboom
+The Yahboom Aimotion K210 module, a compact touchscreen device, now has its first official firmware release.
+
 ### Join Amigo IPS and Amigo TFT firmwares
 Users will be able to flash a single firmware and change display settings if their device was shipped with a display different from standard TFT.
 

docs/getting-started/installing/from-source.en.md

@@ -50,9 +50,9 @@ This will take around an hour or so to complete the first time. Subsequent build
 If all goes well, you should see a new `build` folder containing `firmware.bin` and `kboot.kfpkg` files when the build completes.
 
 ### Reproducibility
-If you build from the `main` branch of the source code, you should be able to reproduce the build process used to generate the last release binaries and obtain an exact copy of the `firmware.bin` file, with a matching hash checksum. The `kboot.kfpkg` file may have a minor difference (1 byte) because it is a zip file, which may embed a timestamp or other local machine attributes.
+If you build from the `main` branch of the source code, you should be able to reproduce the build process used to generate the last release binaries and obtain exact copies of the `firmware.bin` and `kboot.kfpkg` files, with matching hash checksums.
 
-As it is a zip file, you can extract and verify the `firmware.bin` it contains using the following command:
+To extract and verify the firmware.bin contained in kboot.kfpkg, you can use the following command:
 
 ```unzip kboot.kfpkg -d ./kboot/```