From 1a1a1e21674d136a335d3955e0caf250d6af31eb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Henrik=20Tj=C3=A4der?= <henrik@tjaders.com>
Date: Fri, 24 Jan 2020 15:34:41 +0000
Subject: [PATCH] Reference the correct example

---
 book/en/src/by-example/app.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/book/en/src/by-example/app.md b/book/en/src/by-example/app.md
index f6871942ae..5cace3733c 100644
--- a/book/en/src/by-example/app.md
+++ b/book/en/src/by-example/app.md
@@ -103,7 +103,7 @@ mut` variables are safe to use within a hardware task.
 ```
 
 ``` console
-$ cargo run --example interrupt
+$ cargo run --example hardware
 {{#include ../../../../ci/expected/hardware.run}}```
 
 So far all the RTFM applications we have seen look no different that the
@@ -135,7 +135,7 @@ The following example showcases the priority based scheduling of tasks.
 ```
 
 ``` console
-$ cargo run --example interrupt
+$ cargo run --example preempt
 {{#include ../../../../ci/expected/preempt.run}}```
 
 Note that the task `gpiob` does *not* preempt task `gpioc` because its priority