diff --git a/src/06-Driver/14-Subscribing-to-Messages.purs b/src/06-Driver/14-Subscribing-to-Messages.purs
index b6df401..87b985c 100644
--- a/src/06-Driver/14-Subscribing-to-Messages.purs
+++ b/src/06-Driver/14-Subscribing-to-Messages.purs
@@ -35,7 +35,7 @@ main =
 
       io.subscribe $ CR.consumer \raisedIntVal -> do
         liftEffect $ log $
-          "Consumer 1: Button was clicked and produced a random integer \
+          "Consumer 2: Button was clicked and produced a random integer \
           \value: " <> show raisedIntVal <> "\n\
           \\n\
           \Since this consumer uses `pure Nothing`, this consumer \
diff --git a/src/06-Driver/15-Disposing-Components.md b/src/06-Driver/15-Disposing-Components.md
index d49d70a..e15fc7b 100644
--- a/src/06-Driver/15-Disposing-Components.md
+++ b/src/06-Driver/15-Disposing-Components.md
@@ -9,5 +9,4 @@ To compile the next file and view its results in the browser, use these instruct
 ```bash
 spago bundle-app -m Driver.DisposingComponents -t assets/driver/disposing-components.js
 parcel serve assets/driver/disposing-components.html -o disposing-components--parcelified.html --open
-# After the page opens, check your browser's console to see the messages
 ```
diff --git a/src/06-Driver/ReadMe.md b/src/06-Driver/ReadMe.md
index 1a79cd7..6203668 100644
--- a/src/06-Driver/ReadMe.md
+++ b/src/06-Driver/ReadMe.md
@@ -92,7 +92,7 @@ main =
 
 ### Subscribing to Messages Raised by the Top-Level Component
 
-Section's corresponding files: `Message-Subscribing`
+Section's corresponding files: `Subscribing-to-Messages`
 
 When a parent gets notified of a child component's message, it maps the child's message to the parent's action type and handles that action. The `HalogenIO` record type does not have an action type, so we need a different way to respond to messages.
 
diff --git a/src/ReadMe.md b/src/ReadMe.md
index 6b14a2f..fcf862e 100644
--- a/src/ReadMe.md
+++ b/src/ReadMe.md
@@ -1,6 +1,6 @@
 # Learn Halogen
 
-Halogen works by using a tree-like structure where each entity is a `component`. A `component` is a self-contained entity that knows how to render itself based on its current state, can update its state, can detect and handle events, and can communicate with other `component`s in a hierarchial manner.
+Halogen works by using a tree-like structure where each entity is a `component`. A `component` is a self-contained entity that knows how to render itself based on its current state, can update its state, can detect and handle events, and can communicate with other `component`s in a hierarchical manner.
 
 To accomplish all of this, Halogen uses a single `component` type that can be "configured" via 5 other types:
 - the `state` type
@@ -11,7 +11,7 @@ To accomplish all of this, Halogen uses a single `component` type that can be "c
 
 These 5 types are one reason why learning Halogen can be difficult as one can quickly feel overwhelmed by them, especially when new to the Functional Programming paradigm.
 
-To limit this feeling of being overwhelmed, we'll provide some scaffolding that "hides" irrelevent things from you until you understand the foundational concepts first. This scaffolding code will be stored in the `Scaffolding` folder. Feel free to ignore this folder until after you have finished reading through the rest of the folder's contents.
+To limit this feeling of being overwhelmed, we'll provide some scaffolding that "hides" irrelevant things from you until you understand the foundational concepts first. This scaffolding code will be stored in the `Scaffolding` folder. Feel free to ignore this folder until after you have finished reading through the rest of the folder's contents.
 
 ## Outline