From 8413980b076d46908847420accbdb68003d06575 Mon Sep 17 00:00:00 2001
From: WarmongeringBeaver
 <46932488+WarmongeringBeaver@users.noreply.github.com>
Date: Sun, 26 Apr 2020 20:55:32 +0000
Subject: [PATCH] Remove illegal space.

Sorry, I'm the useless-details sheriff.
---
 src/atomics.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/atomics.md b/src/atomics.md
index f750f09..4f55392 100644
--- a/src/atomics.md
+++ b/src/atomics.md
@@ -96,8 +96,8 @@ However there's a third potential state that the hardware enables:
 * `y = 2`: (thread 2 saw `x = 1`, but not `y = 3`, and then overwrote `y = 3`)
 
 It's worth noting that different kinds of CPU provide different guarantees. It
-is common to separate hardware into two categories: strongly-ordered and weakly-
-ordered. Most notably x86/64 provides strong ordering guarantees, while ARM
+is common to separate hardware into two categories: strongly-ordered and weakly-ordered.
+Most notably x86/64 provides strong ordering guarantees, while ARM
 provides weak ordering guarantees. This has two consequences for concurrent
 programming: