From 3b48447934c18264fb9222faa573719079719b4f Mon Sep 17 00:00:00 2001
From: Vincent Esche <regexident@gmail.com>
Date: Tue, 14 Jul 2020 15:40:57 +0200
Subject: Unified spelling of "real-time" (vs. "real time")

(This spelling is consistent with the one provided by Merriam Webster for use an an adjective)
---
 book/en/src/by-example/tasks.md | 2 +-
 book/en/src/preface.md          | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

(limited to 'book')

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/preface.md b/book/en/src/preface.md
index 6563dd4..419f067 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
 
-- 
cgit v1.2.3