From b03f23ab648ecba0a98d8c39cbda7081b6179701 Mon Sep 17 00:00:00 2001
From: Mark Tomlin <Dygear@gmail.com>
Date: Fri, 19 Apr 2024 21:36:03 -0400
Subject: [PATCH] Update sharing_peripherals.adoc

---
 docs/modules/ROOT/pages/sharing_peripherals.adoc | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/docs/modules/ROOT/pages/sharing_peripherals.adoc b/docs/modules/ROOT/pages/sharing_peripherals.adoc
index fcba0e27b..000a7b1de 100644
--- a/docs/modules/ROOT/pages/sharing_peripherals.adoc
+++ b/docs/modules/ROOT/pages/sharing_peripherals.adoc
@@ -8,6 +8,7 @@ The following examples shows different ways to use the on-board LED on a Raspber
 
 Using mutual exclusion is the simplest way to share a peripheral.
 
+TIP: The depenencies you need to run this example link:/book/dev/basic_application.html#_the_cargo_toml[can be found here].
 [,rust]
 ----
 use defmt::*;
@@ -77,6 +78,7 @@ To indicate that the pin will be set to an Output. The `AnyPin` could have been
 
 A channel is another way to ensure exclusive access to a resource. Using a channel is great in the cases where the access can happen at a later point in time, allowing you to enqueue operations and do other things.
 
+TIP: The depenencies you need to run this example link:/book/dev/basic_application.html#_the_cargo_toml[can be found here].
 [,rust]
 ----
 use defmt::*;