diff --git a/readme.md b/readme.md
index 220d72f..225b4a2 100644
--- a/readme.md
+++ b/readme.md
@@ -2,46 +2,24 @@
-- I want to write about worlding around software
-
-
-
-- How do you chose a particular programming language
-- a coding style
-- a development environment and ecosystem
-- an infrastructure where to run the code
-- and so on?
-- These are **not just technical choices**
-- but rather coding contingencies
-
-
-
-- These contingencies are situated in precise contexts
-- economical
-- cultural
-- creative
-- political
-- technical
-- Programming then is not just sharing code, but sharing context.
-- It's providing a perspective to look at the world
-- before attempting to get some grip onto it with a script.
-
-
-
-- How to provide a point of view through the lens of software?
-- Who get to participate in this process of making meaning?
-- How to create a discourse for the code to inhabit?
-- How to stretch the affordances of code?
-- besides
-- technicality
-- marketing
-- advertisement
+How do you chose a particular programming language, a coding style, a development environment and ecosystem, an infrastructure where to run the code, and so on?
+
+These are **not just technical choices**, but rather coding contingencies.
+
+These contingencies are situated in precise economical, cultural, creative, political, and technical contexts. Programming then is not just sharing code, but sharing context. It's providing a perspective to look at the world before attempting to get some grip onto it with a script.
+
+How to offer a point of view through the lens of software?
+Who get to participate in this process of making meaning?
+How to create a discourse for the code to inhabit?
+How to stretch the affordances of code, besides, technicality, marketing, and advertisement?
## Enter documentation
-- Could software documentation
-- _1_ be an ideal surface to build worlds?
-- _2_ be an interface between different knowledges?
-- _3_ be a device to trigger different kind of economy around situated software?
+Could software documentation:
+
+1. be an ideal surface to build worlds?
+2. be an interface between different knowledges?
+3. be a device to trigger different kind of economy around situated software?
-- How can situated practices inform the process of documenting software?
+How can situated practices inform the process of documenting software?
+And how can situated software inform the process of technical writing?