diff --git a/chapters/01_who_is_reading.md b/chapters/01_who_is_reading.md
index c606601..b2291c2 100644
--- a/chapters/01_who_is_reading.md
+++ b/chapters/01_who_is_reading.md
@@ -33,6 +33,7 @@ again versioning tiger ding sun ? --> https://tdingsun.github.io/worlding/
 (did already here --> https://hub.xpub.nl/soupboat/~kamo/projects/api-worldbuilding/ )
 
 ## Getting started
+`(Getting Startled also could make for a nice title)`
 
 Reading undocumented code feels like being an ant walking on a big painting. You can see the strokes of a brush and have an intuition of their direction, but what's missing is an overall idea of how the composition flows. Documentation provides guidance through the bunch of functions and statements that makes software, a bird's eye perspective. It is often the first thing one gets across when approaching a new library or programming language, and it shapes the way a developer thinks about particular piece of code.