diff --git a/chapters/03_hello_worlding.md b/chapters/03_hello_worlding.md
index 172357d..6a419dd 100644
--- a/chapters/03_hello_worlding.md
+++ b/chapters/03_hello_worlding.md
@@ -6,13 +6,15 @@ Here documentation is seen as a surface that could host principles in close cont
 
 __Sections:__  
 
+A structure on how to organize the examples and case studies proposed.
+
 A part of theoretical examples of technology and worlding: Trans\*feminist Servers, Zach Blas, Tiger Ding Sun, James Bridle, Soon and Cox, Richard Gabriel.
 
 A part of case studies. The soupboat. Avantwhatever.net. Queer Motto API. The Screenless Office. The uxn ecosystem. `list wip`
 
 ## Going with the flows
 
-There could be several approaches for making worlds around software. Here are some keywords that refer to the kind of flow these worlding techniques activate. I draft here three directions: to reclaim is to get something back: something that was stolen, or taken away, or lost, or forgotten. To reenchant means to intercept and reorientate towards different directions. To readjust a process, or to move for a different purpose. To reassure serves as a prompt to keep going. It helps making meaning together, and refresh ideas. It offers way to register choices, keep track and share what has been done so far. 
+There could be several approaches for making worlds around software. Here are some keywords that refer to the kind of flow these worlding techniques activate.Drafted here are three directions: to _reclaim_ is to get something back: something that was stolen, or taken away, or lost, or forgotten. To _reenchant_ means to intercept and reorientate towards different directions. To readjust a process, or to move for a different purpose. To _reassure_ serves as a prompt to keep going. It helps making meaning together, and refresh ideas. It offers way to register choices, keep track and share what has been done so far. 
 
 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 renaming them all after the _re_ prefix: to aknowledge their being in progress, again second hand, already contaminated. Borrowed by friends and foes, that had borrowed themselves from someone else. Nonetheless, they offer ways to visualize different strategies to create worlds around software.
 
@@ -21,18 +23,29 @@ reclaim         take back
 reenchant       intercept
 reassure        keep going            
 
-reclaim         renegotiate, recuperate, remember, refuse
-reenchant       reactivate, redirect, rebirth, reboot, rebrand
+reclaim         renegotiate, recuperate, remember, refuse, reactivate
+reenchant       redirect, rebirth, reboot, rebrand
 reassure        refrain, refresh, regret, reaffirm, register, readme
 ```
 
-
 ## reclaim
 
+There seems to be a risk in reducing sociality around software in a conflict between "friends and foes": a risk in reproducing forms of exclusion and violence typical of the IT world. To just swap good and bad, and offer clean solutions. Try instead to apply Chantal Mouffle's concept of agonistic politics to software development intended as struggle between different hegemonic projects.
+
+How can documentation create new spaces around code? Where new spaces means spaces for who are excluded.
 
+Think about the works around queerying technologies, from Zach Blass to Trans\*feminist servers, to Queerying UNIX, to 360 degrees of proximity, the Queer motto API. 
+
+Think about projects related to accessibility, and space built by and for people with diverse ability. Alt-text poetry is a good starting point maybe.
 
 ## reenchant
 
+Three sources that could be explored here relate to an alternative to the model of technosolutionism. 
+
+Staying low
 
+- the plot of her undoing - saidiya hartman
+- federico campagna - technics and magic
+- a way of saying from my dialect about fire and embers
 
 ## reassure