From 04189cc6844d7d43305a57464713defb5a46d85c Mon Sep 17 00:00:00 2001
From: John van der Koijk <33966414+jvanderk@users.noreply.github.com>
Date: Sun, 20 Feb 2022 19:21:25 +0100
Subject: Mostly editorial review.

---
 book/en/src/by-example/app_priorities.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

(limited to 'book/en/src/by-example/app_priorities.md')

diff --git a/book/en/src/by-example/app_priorities.md b/book/en/src/by-example/app_priorities.md
index 1a92ec8..8cee749 100644
--- a/book/en/src/by-example/app_priorities.md
+++ b/book/en/src/by-example/app_priorities.md
@@ -18,8 +18,8 @@ The highest static priority task takes precedence when more than one
 task are ready to execute.
 
 The following scenario demonstrates task prioritization:
-Spawning a higher priority task A during execution of a lower priority task B pends
-task A. Task A has higher priority thus preempting task B which gets suspended
+Spawning a higher priority task A during execution of a lower priority task B suspends
+task B. Task A has higher priority thus preempting task B which gets suspended
 until task A completes execution. Thus, when task A completes task B resumes execution.
 
 ```text
@@ -53,7 +53,8 @@ when `baz`returns. When `bar` returns `foo` can resume.
 
 One more note about priorities: choosing a priority higher than what the device
 supports will result in a compilation error.
-The error is cryptic due to limitations in the language,
+
+The error is cryptic due to limitations in the Rust language
 if `priority = 9` for task `uart0_interrupt` in `example/common.rs` this looks like:
 
 ```text
-- 
cgit v1.2.3