Small fixes.

Makefile

@@ -360,7 +360,7 @@ endif
 ifeq ($(WOOKEY), 1)
 	@echo "$(bold) $(red)  [-] Warning: BITBANG mode is *NOT supported* on the WooKey board ...$(normal)"
 	@echo "$(bold) $(red)  [-] Warning: FLASHER mode is *NOT supported* on the WooKey board ...$(normal)"
-	@echo "$(bold) $(red)      => NOTE: for safety, these features are deactvated in the formware.$(normal)"
+	@echo "$(bold) $(red)      => NOTE: for safety, these features are deactvated in the firmware.$(normal)"
 	@echo "$(bold) $(red)         You can force them in the code while assigning the dedicated GPIOs$(normal)"
 	@echo "$(bold) $(red)         in the WooKey board configuration file (you MUST know what you do).$(normal)"
 	@echo "$(bold) $(red)      => Use it at your own risks!!$(normal)"

README.md

@@ -3,7 +3,8 @@
 
 # NOTICE
 
-This fork critically modifies the delay functionality to work more like a "skip". The reason is because the millisecond count method is too inaccurate imo for attacking live targets.
+This fork critically modifies the delay functionality to work more like a "skip".
+The reason is because the millisecond count method is too inaccurate imo for attacking live targets.
 
 # LEIA Firmware
 
@@ -23,7 +24,7 @@ compilation options are detailed below.
 |                |                      | will vary and must be adapted.       |
 |                |                      |                                      |
 |----------------|----------------------|--------------------------------------|
-| Communication  | USB=1 (default)      | This is the prefered channel used to |
+| Communication  | USB=1 (default)      | This is the preferred channel used to|
 |                | USB=0                | communicate with the board. By       |
 |                |                      | default, two USB /dev/ttyACMx are    |
 |                |                      | used for protocol and debug purposes.|
@@ -64,7 +65,7 @@ compilation options are detailed below.
 |                |                      | embedded on the board).              |
 |                |                      |                                      |
 |----------------|----------------------|--------------------------------------|
-| Debug          | DEBUG=0 (default)    | This activates or desactivates       |
+| Debug          | DEBUG=0 (default)    | This activates or deactivates        |
 |                | DEBUG=1              | the debug console. This console shows|
 |                |                      | the protocol commands and responses  |
 |                |                      | and can help when debugging issues.  |
@@ -98,14 +99,14 @@ to switch from one to another at firmware runtime) using the `set_mode` protocol
 command. When using this command, all the ISO7816 backend will switch from one
 mode to another.
 
-Please beware that the BITBANG mode is interesting, but suffer from obvious
+Please beware that the BITBANG mode is interesting, but suffers from obvious
 limitations when it comes to frequency or "agressive" ETUs: in general, it
 is recommended to stick to an ISO7816 clock frequency of less than 1MHz
 (usually 500 KHz is a conservative value), the issue being that some smart cards
 will not accept such low frequencies. On the ETU side, is is recommended to
 use slow ETUs such as 372, since the agressive ones (e.g. ETU=8) will put the
 bitbanging software handling beyond its limits. Generally speaking, each
-smart card will be different and more or less tolerant when configuring bitbanding.
+smart card will be different and more or less tolerant when configuring bitbanging.
 Additionally, T=0 and T=1 protocols will make a difference here since the T=1
 protocol is inherently more sensible to baud rate.
 
@@ -201,7 +202,11 @@ connected, you can use the `make burn` target to burn the firmware in the board.
 On the DISCO boards (STM32 Discovery F407 and F429), an ST-Link V2 chip is already
 present on the board and you should be able to directly run `make burn` to flash
 the boards. Beware that the mini-USB port is used for flashing, and the micro-USB
-OTG port is used for LEIA protocol and debug /dev/ttyACMx interfaces.
+OTG port is used for LEIA protocol and debug `/dev/ttyACMx` interfaces.
+
+**WARNING: after flashing the board, you might want to at least reset it (and possibly
+unplug/plug the flashing USB interface while leaving the device USB OTG one for Disco boards), so that
+the `/dev/ttyACMx` interfaces are correctly enumerated on the host side.**
 
 # Boards specific pinouts
 
@@ -267,7 +272,7 @@ on the PC host side. Usually, `/dev/ttyACMx` is the protocol console and
 `/dev/ttyACMy` is the debug console when x < y.
 
 **WARNING: beware that some services such as `modemmanager` might interfere with
-the boards proper functionning when they see `/dev/ttyACMx`. You will have to manually
+the boards proper functioning when they see `/dev/ttyACMx`. You will have to manually
 disable such packages for the LEIA firmware nominal usage.**
 
 # The flasher mode