diff --git a/src/ch17-02-concurrency-with-async.md b/src/ch17-02-concurrency-with-async.md
index 36343f15a3..e9346b7c38 100644
--- a/src/ch17-02-concurrency-with-async.md
+++ b/src/ch17-02-concurrency-with-async.md
@@ -274,7 +274,7 @@ there are still a couple of problems. For one thing, the messages do not arrive
at half-second intervals. They arrive all at once, 2 seconds (2,000
milliseconds) after we start the program. For another, this program never exits!
Instead, it waits forever for new messages. You will need to shut it down using
-ctrl-c.
+ctrl-c.
Let’s start by examining why the messages come in all at once after the full
delay, rather than coming in with delays between each one. Within a given async
diff --git a/src/ch17-04-streams.md b/src/ch17-04-streams.md
index 196da5ca1b..340820bad4 100644
--- a/src/ch17-04-streams.md
+++ b/src/ch17-04-streams.md
@@ -345,8 +345,8 @@ which is longer than the other durations we are using. Here, we create a
through the stream, and pin it so that it’s safe to do so. That gets us _almost_
to where we need to be. Everything type checks. If you run this, though, there
will be two problems. First, it will never stop! You’ll need to stop it with
-ctrl-c. Second, the messages from the English
-alphabet will be buried in the midst of all the interval counter messages:
+ctrl-c. Second, the messages from the English alphabet
+will be buried in the midst of all the interval counter messages: