diff --git a/chapters/00. Coding Contingencies.md b/chapters/00. Coding Contingencies.md
index 2244887..6e0c432 100644
--- a/chapters/00. Coding Contingencies.md	
+++ b/chapters/00. Coding Contingencies.md	
@@ -85,9 +85,9 @@ The simulation is structured as a series of stages:
 
     This procedure helps us to think about software as cultural object. Something "deeply woven into contemporary life –economically, culturally, creatively, politically– in manners both obvious and nearly invisible." (Software Studies, 2009), and not just as technical tool existing in a vacuum.
 
-4. **Insert documentation element**
+4. **Introduce documentation**
 
-    Through some iterations, each world will grow a network of actors to play with. Once reached a sufficient mature state, we will introduce a new element: documentation. Throwing a pebble in the puddle to watch how it will ripple through. Which other elements will relate with it, and which one will not? Which transformation it will trigger in the dynamics of access, of power, and representation that are sprouting around software in each simulation?
+    After some iterations each world will grow a network of actors to play with. Once reached a sufficient mature state, we will introduce a new element: documentation. Throwing a pebble in the puddle to watch how it will ripple through. Which other elements will relate with it, and which one will not? Which transformation it will trigger in the dynamics of access, of power, and representation that are sprouting around software in each simulation?
 
     These emerging issues will articulate the main questions of this research: could software documentation be a surface to situate code in the world? Could it be a device to foster entry points for a more diverse participation? Could it be a way to orientate technologies with our set of values?