From e9fa71c065add03b9aedfb0e848b115370732b3c Mon Sep 17 00:00:00 2001 From: Vincent Esche Date: Tue, 14 Jul 2020 16:01:14 +0200 Subject: [PATCH] Fixed some more spelling --- book/en/src/SUMMARY.md | 1 + book/en/src/by-example/app.md | 2 +- book/en/src/by-example/tips.md | 4 ++-- 3 files changed, 4 insertions(+), 3 deletions(-) diff --git a/book/en/src/SUMMARY.md b/book/en/src/SUMMARY.md index 305c1a0e53..25aef811b9 100644 --- a/book/en/src/SUMMARY.md +++ b/book/en/src/SUMMARY.md @@ -1,6 +1,7 @@ # Summary [Preface](./preface.md) + - [RTIC by example](./by-example.md) - [The `app` attribute](./by-example/app.md) - [Resources](./by-example/resources.md) diff --git a/book/en/src/by-example/app.md b/book/en/src/by-example/app.md index bff516d253..e0f4f941ec 100644 --- a/book/en/src/by-example/app.md +++ b/book/en/src/by-example/app.md @@ -90,7 +90,7 @@ $ cargo run --example idle To declare interrupt handlers the framework provides a `#[task]` attribute that can be attached to functions. This attribute takes a `binds` argument whose value is the name of the interrupt to which the handler will be bound to; the -function adornated with this attribute becomes the interrupt handler. Within the +function adorned with this attribute becomes the interrupt handler. Within the framework these type of tasks are referred to as *hardware* tasks, because they start executing in reaction to a hardware event. diff --git a/book/en/src/by-example/tips.md b/book/en/src/by-example/tips.md index ce9bba8254..b191b9dab4 100644 --- a/book/en/src/by-example/tips.md +++ b/book/en/src/by-example/tips.md @@ -155,7 +155,7 @@ const APP: () = { }; ``` -Or, you can use the [`cargo-expand`] subcommand. This subcommand will expand +Or, you can use the [`cargo-expand`] sub-command. This sub-command will expand *all* the macros, including the `#[rtic::app]` attribute, and modules in your crate and print the output to the console. @@ -169,7 +169,7 @@ $ cargo expand --example smallest | tail ## Resource de-structure-ing When having a task taking multiple resources it can help in readability to split -up the resource struct. Here're two examples on how this can be done: +up the resource struct. Here are two examples on how this can be done: ``` rust {{#include ../../../../examples/destructure.rs}}