diff options
| -rw-r--r-- | docs/pages/new_project.adoc | 2 | ||||
| -rw-r--r-- | docs/pages/sharing_peripherals.adoc | 4 | ||||
| -rw-r--r-- | docs/pages/time_keeping.adoc | 4 |
3 files changed, 5 insertions, 5 deletions
diff --git a/docs/pages/new_project.adoc b/docs/pages/new_project.adoc index 346d9f0f8..821bcbd27 100644 --- a/docs/pages/new_project.adoc +++ b/docs/pages/new_project.adoc | |||
| @@ -1,6 +1,6 @@ | |||
| 1 | = Starting a new project | 1 | = Starting a new project |
| 2 | 2 | ||
| 3 | Once you’ve successfully xref:getting_started.adoc[run some example projects], the next step is to make a standalone Embassy project. | 3 | Once you’ve successfully xref:#_getting_started[run some example projects], the next step is to make a standalone Embassy project. |
| 4 | 4 | ||
| 5 | == Tools for generating Embassy projects | 5 | == Tools for generating Embassy projects |
| 6 | 6 | ||
diff --git a/docs/pages/sharing_peripherals.adoc b/docs/pages/sharing_peripherals.adoc index 6ba13f93b..dfb8c1ffe 100644 --- a/docs/pages/sharing_peripherals.adoc +++ b/docs/pages/sharing_peripherals.adoc | |||
| @@ -8,7 +8,7 @@ The following examples shows different ways to use the on-board LED on a Raspber | |||
| 8 | 8 | ||
| 9 | Using mutual exclusion is the simplest way to share a peripheral. | 9 | Using mutual exclusion is the simplest way to share a peripheral. |
| 10 | 10 | ||
| 11 | TIP: Dependencies needed to run this example link:/book/dev/basic_application.html#_the_cargo_toml[can be found here]. | 11 | TIP: Dependencies needed to run this example link:#_the_cargo_toml[can be found here]. |
| 12 | [,rust] | 12 | [,rust] |
| 13 | ---- | 13 | ---- |
| 14 | use defmt::*; | 14 | use defmt::*; |
| @@ -78,7 +78,7 @@ To indicate that the pin will be set to an Output. The `AnyPin` could have been | |||
| 78 | 78 | ||
| 79 | 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. | 79 | 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. |
| 80 | 80 | ||
| 81 | TIP: Dependencies needed to run this example link:/book/dev/basic_application.html#_the_cargo_toml[can be found here]. | 81 | TIP: Dependencies needed to run this example link:#_the_cargo_toml[can be found here]. |
| 82 | [,rust] | 82 | [,rust] |
| 83 | ---- | 83 | ---- |
| 84 | use defmt::*; | 84 | use defmt::*; |
diff --git a/docs/pages/time_keeping.adoc b/docs/pages/time_keeping.adoc index 17492a884..11ddb2b2b 100644 --- a/docs/pages/time_keeping.adoc +++ b/docs/pages/time_keeping.adoc | |||
| @@ -16,7 +16,7 @@ The `embassy::time::Timer` type provides two timing methods. | |||
| 16 | 16 | ||
| 17 | An example of a delay is provided as follows: | 17 | An example of a delay is provided as follows: |
| 18 | 18 | ||
| 19 | TIP: Dependencies needed to run this example link:/book/dev/basic_application.html#_the_cargo_toml[can be found here]. | 19 | TIP: Dependencies needed to run this example link:#_the_cargo_toml[can be found here]. |
| 20 | [,rust] | 20 | [,rust] |
| 21 | ---- | 21 | ---- |
| 22 | use embassy::executor::{task, Executor}; | 22 | use embassy::executor::{task, Executor}; |
| @@ -41,7 +41,7 @@ that expect a generic delay implementation to be provided. | |||
| 41 | 41 | ||
| 42 | An example of how this can be used: | 42 | An example of how this can be used: |
| 43 | 43 | ||
| 44 | TIP: Dependencies needed to run this example link:/book/dev/basic_application.html#_the_cargo_toml[can be found here]. | 44 | TIP: Dependencies needed to run this example link:#_the_cargo_toml[can be found here]. |
| 45 | [,rust] | 45 | [,rust] |
| 46 | ---- | 46 | ---- |
| 47 | use embassy::executor::{task, Executor}; | 47 | use embassy::executor::{task, Executor}; |