Merge #741

741: Docs 2 r=korken89 a=datdenkikniet

Working on the migration guide and other docs

TODO:
- [x] Migration guide
- [x] Hardcoded examples should link to example code that is tested (this was already done, AFAICT)
- [x] Address #699 
- [x] Discuss: should we remove references to non-v2, apart from the migration guide and link to the book for v1? (Off-github conclusion: yes)
- [x] RTIC {vs,and} Embassy (important: distinction between embassy runtime & HALs)
- [x] More descriptive docs on how to implement & PR implementations of `Monotonic` to `rtic-monotonics` 


Co-authored-by: datdenkikniet <jcdra1@gmail.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/book/en/src/by-example/message_passing.md b/book/en/src/by-example/message_passing.md
index 0dc8f85..02fd298 100644
--- a/book/en/src/by-example/message_passing.md
+++ b/book/en/src/by-example/message_passing.md
@@ -3,14 +3,14 @@
 Software tasks support message passing, this means that software tasks can be spawned
 with an argument: `foo::spawn(1)` which will run the task `foo` with the argument `1`.
 
-Capacity sets the size of the spawn queue for the task, if not specified capacity defaults to 1.
+Capacity sets the size of the spawn queue for the task. If it is not specified, the capacity defaults to 1.
 
 In the example below, the capacity of task `foo` is `3`, allowing three simultaneous
 pending spawns of `foo`. Exceeding this capacity is an `Error`.
 
 The number of arguments to a task is not limited:
 
-``` rust
+``` rust,noplayground
 {{#include ../../../../examples/message_passing.rs}}
 ```