diff --git a/book/en/src/by-example/resources.md b/book/en/src/by-example/resources.md
index 9f2c6c577f..0b69c4dba4 100644
--- a/book/en/src/by-example/resources.md
+++ b/book/en/src/by-example/resources.md
@@ -6,7 +6,7 @@ storage and safe accesses without the use of `unsafe` code.
 RTIC resources are visible only to functions declared within the `#[app]` module and the framework
 gives the user complete control (on a per-task basis) over resource accessibility.
 
-Declaration of system-wide resources are by annotating **two** `struct`s within the `#[app]` module
+Declaration of system-wide resources is done by annotating **two** `struct`s within the `#[app]` module
 with the attribute `#[local]` and `#[shared]`.
 Each field in these structures corresponds to a different resource (identified by field name).
 The difference between these two sets of resources will be covered below.
diff --git a/book/en/src/by-example/software_tasks.md b/book/en/src/by-example/software_tasks.md
index 370792f841..f244ca68b1 100644
--- a/book/en/src/by-example/software_tasks.md
+++ b/book/en/src/by-example/software_tasks.md
@@ -10,7 +10,7 @@ bound interrupt vector.
 These free interrupts used as dispatchers are interrupt vectors not used by hardware tasks.
 
 The `#[task]` attribute used on a function declare it as a software tasks.
-The static method `task_name::spawn()` spawn (start) a software task and
+The static method `task_name::spawn()` spawns (starts) a software task and
 given that there are no higher priority tasks running the task will start executing directly.
 
 A list of “free” and usable interrupts allows the framework to dispatch software tasks.