diff options
| -rw-r--r-- | Cargo.toml | 2 | ||||
| -rw-r--r-- | README.md | 2 | ||||
| -rw-r--r-- | book/en/src/by-example/tasks.md | 2 | ||||
| -rw-r--r-- | book/en/src/preface.md | 2 |
4 files changed, 4 insertions, 4 deletions
@@ -5,7 +5,7 @@ authors = [ "Per Lindgren <per.lindgren@ltu.se>", ] categories = ["concurrency", "embedded", "no-std"] -description = "Real-Time Interrupt-driven Concurrency (RTIC): a concurrency framework for building real time systems" +description = "Real-Time Interrupt-driven Concurrency (RTIC): a concurrency framework for building real-time systems" documentation = "https://rtic.rs/" edition = "2018" keywords = ["arm", "cortex-m"] @@ -1,6 +1,6 @@ # Real-Time Interrupt-driven Concurrency -A concurrency framework for building real time systems. +A concurrency framework for building real-time systems. Formerly known as Real-Time For the Masses. diff --git a/book/en/src/by-example/tasks.md b/book/en/src/by-example/tasks.md index 5978ca83..d0b5acb9 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/preface.md b/book/en/src/preface.md index 6563dd4d..419f067e 100644 --- a/book/en/src/preface.md +++ b/book/en/src/preface.md @@ -1,6 +1,6 @@ <h1 align="center">Real-Time Interrupt-driven Concurrency</h1> -<p align="center">A concurrency framework for building real time systems</p> +<p align="center">A concurrency framework for building real-time systems</p> # Preface |