3 files changed, 4 insertions, 4 deletions
diff --git a/book/en/src/by-example/app.md b/book/en/src/by-example/app.md
index bff516d..e0f4f94 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/tasks.md b/book/en/src/by-example/tasks.md
index 5978ca8..d0b5acb 100644
--- a/book/en/src/by-example/tasks.md
+++ b/book/en/src/by-example/tasks.md
@@ -78,7 +78,7 @@ message. In most scenarios spawning errors are handled in one of two ways:
   platform can deal with peak payload or if the processor needs to be replaced
   with a faster one.
 
-- Ignoring the result. In soft real time and non real time applications it may
+- Ignoring the result. In soft real-time and non real-time applications it may
   be OK to occasionally lose data or fail to respond to some events during event
   bursts. In those scenarios silently letting a `spawn` call fail may be
   acceptable.
diff --git a/book/en/src/by-example/tips.md b/book/en/src/by-example/tips.md
index ce9bba8..b191b9d 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}}