Fixed some more spelling

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)

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.
 

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}}