From 5a09b7aca411aa42fd8405b09586dbc0f478ed2b Mon Sep 17 00:00:00 2001
From: "the Phoeron\" Colin J.E. Lupton" <thephoeron@protonmail.com>
Date: Mon, 29 Aug 2022 15:12:11 -0400
Subject: [PATCH] Update Exercise 1.1.8, Configuring Your Development
 Environment

---
 1-01-08-configuration.md | 9 ++++++---
 CHANGELOG.md             | 6 ++++++
 2 files changed, 12 insertions(+), 3 deletions(-)

diff --git a/1-01-08-configuration.md b/1-01-08-configuration.md
index d01a5a6..685a0e4 100644
--- a/1-01-08-configuration.md
+++ b/1-01-08-configuration.md
@@ -117,16 +117,19 @@ All you need to get started with Lisp is a simple, no-frills text editor with sy
   * Sublime Text
   * Atom
   * UltraEdit
+  * gedit
+* macOS only
+  * BBEdit
 * Windows only
   * Notepad++
 
-Other popular text and code editors, such as BBedit, TextWrangler, and Gedit, do not have syntax highlighting for Lisp.
+Your favourite existing text editor should also be fine, just make sure it has syntax highlighting for Lisp and stays out of your way.
 
 ### Working From the Command-Line
 
 (writing notes)
 
 - Importance of being comfortable with the Command-Line
-- Running and Compiling Lisp from the Command-Line
+- Running and Compiling Lisp source-code files from the Command-Line
 - Lisp shell scripts
-- Launching the REPL
+- Launching the REPL for interactive development
diff --git a/CHANGELOG.md b/CHANGELOG.md
index cdb4e1b..472010e 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,11 @@
 # CHANGELOG
 
+## 2022-08-29
+
+- Exercise 1.1.8, "Configuring Your Development Environment"
+    - Revise subsection on choice of text editors because my information was woefully out-of-date
+    - Minor clarifications to subsection on being comfortable at the command-line as I think exactly how to word it
+
 ## 2022-08-26
 
 - Fix syntax highlighting for Exercise 1.5.12, "More Tries"
-- 
GitLab