diff options
| -rw-r--r-- | book/en/src/migration_v1_v2.md | 2 | ||||
| -rw-r--r-- | book/en/src/starting_a_project.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/book/en/src/migration_v1_v2.md b/book/en/src/migration_v1_v2.md index 96fa231..173b964 100644 --- a/book/en/src/migration_v1_v2.md +++ b/book/en/src/migration_v1_v2.md @@ -9,7 +9,7 @@ Migrating a project from RTIC `v1.0.x` to `v2.0.0` involves the following steps: For a detailed description of the changes, refer to the subchapters. -If you wish to see a code example of changes required, you can check out [the full example migration page](./migration_v2/complete_example.md). +If you wish to see a code example of changes required, you can check out [the full example migration page](./migration_v1_v2/complete_example.md). #### TL;DR (Too Long; Didn't Read) 1. Add `#![type_alias_impl_trait]` to your crate, and use `cargo +nightly`. diff --git a/book/en/src/starting_a_project.md b/book/en/src/starting_a_project.md index ae979f4..437248f 100644 --- a/book/en/src/starting_a_project.md +++ b/book/en/src/starting_a_project.md @@ -3,7 +3,7 @@ A recommendation when starting a RTIC project from scratch is to follow RTIC's [`defmt-app-template`]. -If you are targeting ARMv6-M or ARMv8-M-base architecture, check out the section [Target Architecture](../internals/targets.md) for more information on hardware limitations to be aware of. +If you are targeting ARMv6-M or ARMv8-M-base architecture, check out the section [Target Architecture](./internals/targets.md) for more information on hardware limitations to be aware of. [`defmt-app-template`]: https://github.com/rtic-rs/defmt-app-template |