diff --git a/yotta/data/example-authcrypt/README.md b/yotta/data/example-authcrypt/README.md
index 55186d1..0a46a13 100644
--- a/yotta/data/example-authcrypt/README.md
+++ b/yotta/data/example-authcrypt/README.md
@@ -28,27 +28,19 @@
     yotta target frdm-k64f-gcc
     ```
 
-4. Check that there are no missing dependencies:
-
-    ```
-    $ yt ls
-    ```
-
-    If there are, yotta will list them in the terminal. Please install them before proceeding.
-
-5. Build mbedtls and the examples. This will take a long time if it is the first time:
+4. Build mbedtls and the examples. This will take a long time if it is the first time:
 
     ```
     $ yt build
     ```
 
-6. Copy `build/frdm-k64f-gcc/test/mbedtls-test-example-authcrypt.bin` to your mbed board and wait until the LED next to the USB port stops blinking.
+5. Copy `build/frdm-k64f-gcc/test/mbedtls-test-example-authcrypt.bin` to your mbed board and wait until the LED next to the USB port stops blinking.
 
-7. Start the serial terminal emulator and connect to the virtual serial port presented by FRDM-K64F. For settings, use 115200 baud, 8N1, no flow control. **Warning:** for this example, the baud rate is not the default 9600, it is 115200.
+6. Start the serial terminal emulator and connect to the virtual serial port presented by FRDM-K64F. For settings, use 115200 baud, 8N1, no flow control. **Warning:** for this example, the baud rate is not the default 9600, it is 115200.
 
-8. Press the reset button on the board.
+7. Press the reset button on the board.
 
-9. The output in the terminal window should look like:
+8. The output in the terminal window should look like:
 
     ```
     {{timeout;10}}
diff --git a/yotta/data/example-benchmark/README.md b/yotta/data/example-benchmark/README.md
index dfdc965..8449cbc 100644
--- a/yotta/data/example-benchmark/README.md
+++ b/yotta/data/example-benchmark/README.md
@@ -28,27 +28,19 @@
     yotta target frdm-k64f-gcc
     ```
 
-4. Check that there are no missing dependencies:
-
-    ```
-    $ yt ls
-    ```
-
-    If there are, yotta will list them in the terminal. Please install them before proceeding.
-
-5. Build mbedtls and the examples. This will take a long time if it is the first time:
+4. Build mbedtls and the examples. This will take a long time if it is the first time:
 
     ```
     $ yt build
     ```
 
-6. Copy `build/frdm-k64f-gcc/test/mbedtls-test-example-benchmark.bin` to your mbed board and wait until the LED next to the USB port stops blinking.
+5. Copy `build/frdm-k64f-gcc/test/mbedtls-test-example-benchmark.bin` to your mbed board and wait until the LED next to the USB port stops blinking.
 
-7. Start the serial terminal emulator and connect to the virtual serial port presented by FRDM-K64F. For settings, use 115200 baud, 8N1, no flow control. **Warning:** for this example, the baud rate is not the default 9600, it is 115200.
+6. Start the serial terminal emulator and connect to the virtual serial port presented by FRDM-K64F. For settings, use 115200 baud, 8N1, no flow control. **Warning:** for this example, the baud rate is not the default 9600, it is 115200.
 
-8. Press the reset button on the board.
+7. Press the reset button on the board.
 
-9. The output in the terminal window should look like:
+8. The output in the terminal window should look like:
 
     ```
     {{timeout;150}}
diff --git a/yotta/data/example-hashing/README.md b/yotta/data/example-hashing/README.md
index ed941cf..57d7cf3 100644
--- a/yotta/data/example-hashing/README.md
+++ b/yotta/data/example-hashing/README.md
@@ -28,27 +28,19 @@
     yotta target frdm-k64f-gcc
     ```
 
-4. Check that there are no missing dependencies:
-
-    ```
-    $ yt ls
-    ```
-
-    If there are, yotta will list them in the terminal. Please install them before proceeding.
-
-5. Build mbedtls and the examples. This will take a long time if it is the first time:
+4. Build mbedtls and the examples. This will take a long time if it is the first time:
 
     ```
     $ yt build
     ```
 
-6. Copy `build/frdm-k64f-gcc/test/mbedtls-test-example-hashing.bin` to your mbed board and wait until the LED next to the USB port stops blinking.
+5. Copy `build/frdm-k64f-gcc/test/mbedtls-test-example-hashing.bin` to your mbed board and wait until the LED next to the USB port stops blinking.
 
-7. Start the serial terminal emulator and connect to the virtual serial port presented by FRDM-K64F. For settings, use 115200 baud, 8N1, no flow control. **Warning:** for this example, the baud rate is not the default 9600, it is 115200.
+6. Start the serial terminal emulator and connect to the virtual serial port presented by FRDM-K64F. For settings, use 115200 baud, 8N1, no flow control. **Warning:** for this example, the baud rate is not the default 9600, it is 115200.
 
-8. Press the reset button on the board.
+7. Press the reset button on the board.
 
-9. The output in the terminal window should look like:
+8. The output in the terminal window should look like:
 
     ```
     {{timeout;10}}
diff --git a/yotta/data/example-selftest/README.md b/yotta/data/example-selftest/README.md
index 0ded404..d060219 100644
--- a/yotta/data/example-selftest/README.md
+++ b/yotta/data/example-selftest/README.md
@@ -28,27 +28,19 @@
     yotta target frdm-k64f-gcc
     ```
 
-4. Check that there are no missing dependencies:
-
-    ```
-    $ yt ls
-    ```
-
-    If there are, yotta will list them in the terminal. Please install them before proceeding.
-
-5. Build mbedtls and the examples. This will take a long time if it is the first time:
+4. Build mbedtls and the examples. This will take a long time if it is the first time:
 
     ```
     $ yt build
     ```
 
-6. Copy `build/frdm-k64f-gcc/test/mbedtls-test-example-selftest.bin` to your mbed board and wait until the LED next to the USB port stops blinking.
+5. Copy `build/frdm-k64f-gcc/test/mbedtls-test-example-selftest.bin` to your mbed board and wait until the LED next to the USB port stops blinking.
 
-7. Start the serial terminal emulator and connect to the virtual serial port presented by FRDM-K64F. For settings, use 115200 baud, 8N1, no flow control. **Warning:** for this example, the baud rate is not the default 9600, it is 115200.
+6. Start the serial terminal emulator and connect to the virtual serial port presented by FRDM-K64F. For settings, use 115200 baud, 8N1, no flow control. **Warning:** for this example, the baud rate is not the default 9600, it is 115200.
 
-8. Press the reset button on the board.
+7. Press the reset button on the board.
 
-9. The output in the terminal window should look like:
+8. The output in the terminal window should look like:
 
     ```
     {{timeout;40}}
diff --git a/yotta/data/example-tls-client/README.md b/yotta/data/example-tls-client/README.md
index beddd7b..4a798f6 100644
--- a/yotta/data/example-tls-client/README.md
+++ b/yotta/data/example-tls-client/README.md
@@ -34,27 +34,19 @@
     yotta target frdm-k64f-gcc
     ```
 
-5. Check that there are no missing dependencies:
-
-    ```
-    $ yt ls
-    ```
-
-    If there are, yotta will list them in the terminal. Please install them before proceeding.
-
 5. Build mbedtls and the examples. This will take a long time if it is the first time:
 
     ```
     $ yt build
     ```
 
-7. Copy `build/frdm-k64f-gcc/test/mbedtls-test-example-tls-client.bin` to your mbed board and wait until the LED next to the USB port stops blinking.
+6. Copy `build/frdm-k64f-gcc/test/mbedtls-test-example-tls-client.bin` to your mbed board and wait until the LED next to the USB port stops blinking.
 
-8. Start the serial terminal emulator and connect to the virtual serial port presented by FRDM-K64F. For settings, use 115200 baud, 8N1, no flow control. **Warning:** for this example, the baud rate is not the default 9600, it is 115200.
+7. Start the serial terminal emulator and connect to the virtual serial port presented by FRDM-K64F. For settings, use 115200 baud, 8N1, no flow control. **Warning:** for this example, the baud rate is not the default 9600, it is 115200.
 
-9. Press the reset button on the board.
+8. Press the reset button on the board.
 
-10. The output in the terminal window should look like:
+9. The output in the terminal window should look like:
 
     ```
     {timeout;120}}