diff --git a/chapters/00_intro.md b/chapters/00_intro.md
index accca73..08a185b 100644
--- a/chapters/00_intro.md
+++ b/chapters/00_intro.md
@@ -1,4 +1,4 @@
-## Coding contingencies
+## 0. Coding contingencies
 
 ```todo
 - how to quote propperly an introduction from a book series? (software studies)
diff --git a/chapters/01_who_is_reading.md b/chapters/01_who_is_reading.md
index 34d079d..ca71726 100644
--- a/chapters/01_who_is_reading.md
+++ b/chapters/01_who_is_reading.md
@@ -1,4 +1,4 @@
-## Who is reading
+## 1. Who is reading
 
 ```note
 documentation as a publishing surface?
@@ -27,7 +27,7 @@ The introduction to a program situates it also within a larger ecosystem: how to
 
 The initial imprinting of documentation is a vantage point to orientate code in the world.
 
-## A code companion
+### A code companion
 
 The devil is in the details, and software as well: the translation between human and machine has to be negotiated with all the specifics of a particular programming language or platform. Sometimes for the web, sometimes for a hardware component, sometimes for another operative system. These _specs_ make every piece of code a bit alien and peculiar. Tinkering with code is not just knowing by heart a programming language, but rather having to deal with a lot of different recipes for different occasions, and know how to adapt.
 
@@ -43,7 +43,7 @@ A text that fails to address who's reading can result inaccessible and frustrati
 
 The same is true for the additional layers of meaning necessary for a process of world building. To enchant software with political aesthetic (Ranciérre through Soon and Cox, 2020) is required to operate at different scales. Within both public and private dimensions, with technical and social frameworks. During a workshop for example, people meet face to face. Here togetherness can glue technicalities as a paratext, questioning reproduction of knowledge and its power dynamics. (See for example _Feminists Federating_, mara karagianni, ooooo, nate wessalowski, vo ezn in Toward a Minor Tech - A peer reviewed Newspaper vol 12, 2023) (Note that the opposite effect is also true, with technicalities as paratext conditioning how people are together)
 
-## Welcoming writing
+### Welcoming writing
 
 The potential of documentation to orientate software in the world clashes against some big elephants in the room, and tech culture should stop keep them in captivity. Sure, it would be nice if developers could rely on several kinds of documentation when approaching code. Unfortunately often there is not even one available.
 
@@ -71,7 +71,7 @@ lowering barriers
 -   aesthetic programming
 -   welcome.js (bridle, 2016)
 ```
-## "Natural" reader
+### "Natural" reader
 
 ```note
 -   assuming a certain kind of reader - expert - dude
diff --git a/chapters/03_hello_worlding.md b/chapters/03_hello_worlding.md
index e5ad424..89f481b 100644
--- a/chapters/03_hello_worlding.md
+++ b/chapters/03_hello_worlding.md
@@ -1,4 +1,4 @@
-## Hello worlding
+## 3. Hello worlding
 
 The third section is focused on worlding, and the relation between code, documentation practices and political aesthetic.
 
@@ -18,6 +18,7 @@ There could be several approaches for making worlds around software. Here are so
 
 These labels are open and loose, overlapping and not mutually exclusive, temporary and on the move. They are meant to change, to expire fast, and going bad even faster: they require continuous treatments and repeated efforts. That's why I'm naming them all after the _re_ prefix: to aknowledge their being in progress, second hand again, already contaminated. Borrowed by friends and foes, that had borrowed themselves from someone else. One should diffidate of these categories because they're instable. Nonetheless, they offer ways to visualize different strategies to create worlds around software.
 
+
 ```
 reclaim         take back
 reenchant       intercept