diff --git a/Documentation/HOWTO-change-firmware-and-compile-it_MeesElectronics.md b/Documentation/HOWTO-change-firmware-and-compile-it_MeesElectronics.md
index 2b02cae..73d9b95 100644
--- a/Documentation/HOWTO-change-firmware-and-compile-it_MeesElectronics.md
+++ b/Documentation/HOWTO-change-firmware-and-compile-it_MeesElectronics.md
@@ -1,4 +1,4 @@
-# How to compile the rnode firmware yourself
+# How to compile the RNode firmware yourself
 
 ## Required knowledge
 
@@ -317,15 +317,13 @@ Than flash the firmware:
 
     $ make upload-waveshare-esp32-s3-pico
 
-This will end with error 'This device has not been provisioned yet, cannot set firmware hash'. But fear not. After flashing a custom board, you will also need to provision the EEPROM before use:
+This first time you flash a new board, this command will end with the error `This device has not been provisioned yet, cannot set firmware hash`. That is because the EEPROM is not programmes yet You will need to provision the EEPROM before use:
 
     $ rnodeconf /dev/ttyACM0 -r --platform ESP32 --model a4 --product f0 --hwrev 3
 
-Sometimes the board give error whule flashing. Try flashing the board via the other serial interface (ttyACM1). Don't know why, but it works.
-
 ### Migrating to a other system
 
-When the rnode is flashed, it is signed with a key. If you connect the rnode to another system, this key cannot be validated. It is possible to write a new key to the rnode by erasing the eeprom and writing the local key to it.
+When the rnode is flashed, it is signed with a key. If you connect the RNode to another system, this key cannot be validated. It is possible to write a new key to the RNode by erasing the eeprom and writing the local key to it.
 
     $ rnodeconf /dev/ttyACM0 --eeprom-wipe
     $ rnodeconf /dev/ttyACM0 -r --platform ESP32 --model a4 --product f0 --hwrev 3