From 8e0090099623f7a1aba7924a85d0ca258d204d04 Mon Sep 17 00:00:00 2001 From: Ashok Argent-Katwala Date: Thu, 30 Apr 2026 07:58:34 -0400 Subject: [PATCH] Add trailing whitespace to chapter 2. This appears to fix a problem where chapter 3 is not recognized as a chapter, and drops the introductory text (in Asciidoctor 2.0.26). It would also work to add this newline above the chapter 3 title, but I think this makes more sense. I haven't read the asciidoc syntax in detail, and the file does have an existing terminal newline, but presumably it expects multiple newlines to work correctly in this particular circumstance. --- chapter-2-how-we-make-decisions.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/chapter-2-how-we-make-decisions.adoc b/chapter-2-how-we-make-decisions.adoc index d58fb11..63ff08b 100644 --- a/chapter-2-how-we-make-decisions.adoc +++ b/chapter-2-how-we-make-decisions.adoc @@ -202,3 +202,4 @@ Gather a group of your software engineering colleagues and discuss the following . When was the last time we talked about how we read code? Specifically, about how we do the reading, not about the code we read. . Do we have models of our system that allow us to investigate performance issues programmatically? What about security concerns? Or business domain events? . How do we obtain our architecture diagrams? Are they manually created, or do we generate them out of the system’s sources? How confident are we that the diagrams we use represent the system accurately? How would we verify this? +