From c63306d70fc8d606f1a039f7c6843496c037c23f Mon Sep 17 00:00:00 2001 From: Viktor Zahorodnii Date: Tue, 10 Mar 2026 12:30:37 +0200 Subject: [PATCH] Fix chapter reference in using-a-driver.md --- mdbook/src/12-i2c/using-a-driver.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mdbook/src/12-i2c/using-a-driver.md b/mdbook/src/12-i2c/using-a-driver.md index 3ef24cee..029e4bb9 100644 --- a/mdbook/src/12-i2c/using-a-driver.md +++ b/mdbook/src/12-i2c/using-a-driver.md @@ -3,7 +3,7 @@ As we already discussed in chapter 5 `embedded-hal` provides abstractions which can be used to write platform independent code that can interact with hardware. In fact all the methods we have used to interact with hardware -in chapter 7 and up until now in chapter 8 were from traits, defined by `embedded-hal`. +in chapter [LED roulette](../07-led-roulette/index.html) and up until now in this chapter were from traits, defined by `embedded-hal`. Now we'll make actual use of the traits `embedded-hal` provides for the first time. It would be pointless to implement a driver for our LSM303AGR for every platform