kernel-labs: Fix description of LEDs behavior

Signed-off-by: Miquel Raynal <[email protected]>

labs/kernel-i2c-describing-hardware/kernel-i2c-describing-hardware.tex

@@ -95,13 +95,13 @@ \section{Driving LEDs}
 \code{default-state} property of each LED subnode.
 
 Reboot the board using the new DTS and observe the LEDs default states
-change, except one of them which will not turn on. It is expected. If
-you look again at the common file defining the LEDs, they are actually
-all linked to a \code{linux,default-trigger}. The default state only
-applies until the trigger starts its activity. The one that remains off
-is actually driven by the eMMC trigger, you can try to make it blink by
-creating a bit of activity on the eMMC bus (but do not overwrite its
-content!).
+change, except one of them which will rapidly turn back off. It is
+expected. If you look again at the common file defining the LEDs, they
+are actually all linked to a \code{linux,default-trigger}. The default
+state only applies until the trigger starts its activity. The one
+quickly turns off is actually driven by the eMMC trigger, you can try to
+make it blink by creating a bit of activity on the eMMC bus (but do not
+overwrite its content!).
 
 One of the remaining LEDs is driven by the SD card and the other is
 supposed to be a heartbeat, which you can enable with