diff --git a/projects/gpp/documentation.md b/projects/gpp/documentation.md
index 3c260d5..e398e61 100644
--- a/projects/gpp/documentation.md
+++ b/projects/gpp/documentation.md
@@ -41,10 +41,14 @@ Set some references by looking back at the works made last year and read them th
 
 Expand the research to tap into ongoing projects outside XPUB, such as freelance works and [parallel research](../ooc-summer-session/). Are there ways to make the documentation process more sustainable? Are there strategies to overcome a low-resources environment? What are the relations between documentation and the communities around a software?
 
+<!-- TODO: inflate this ^ -->
+
 Question the nature of the documentation: what does it take for granted? For what kind of public it is produced, and what kind of public does it produce? How does it normalize the context around the software? What are its politics of access? How does it create entry points and how does it gatekeep?
 
 Try to infiltrate the industry of software development through documentation. Attempt to expose their public to these questions in subtle ways. Offer entry points and escape routes from the universal solution proposed by big corporates.
 
+<!-- TODO: this more concrete approach here -->
+
 <!-- There are three main nodes in the graph of this project. Writing software, taking care, and staying low. -->
 
 <!-- Writing software and taking care are meant to be moments of research and curation of contents in the form of resources, experiences and approaches. Starting from the assumption that there is no universal solution for writing software, and that coding is always site specific, this research could set some coordinates by looking back at the works made last year and analyze them through the lenses of code and care. -->
@@ -71,6 +75,8 @@ Think about a glossary and possible formats to test some concept in a small scal
 
 Experiment writing the documentation for the [Padliography](https://hub.xpub.nl/soupboat/padliography/) and the [Workbook](https://hub.xpub.nl/soupboat/workbook/).
 
+<!-- TODO: provide some context about padliography and workbook -->
+
 **November**
 
 Work on OOC for December performance at NaO Festival, Milan. What does it mean to document a bespoke tool developed just for this project? Experiment with the documentation for the interactive patch of OOC.
@@ -133,7 +139,7 @@ To make software means not only to write code, but also to create a context and
 
 Documentation is a space that interfaces the different actors around software. Software documentation is a space with potential to renegotiate and reclaim given margins and entry points. It is a chance to overwrite what is normalized, and let different knowledges and voices participate in the discourse around software.
 
-Documenting software it's a complex practice. Documenting software is a process of translation. Writing documentation it's more difficult than writing software itself. It requires a lot of time and energy, and it involves many different skills: writing, coding, knowing how to share and at which intensity. It's a collaborative practice that could open to different voices.
+Documenting software is a complex practice. Documenting software is a process of translation. Writing documentation it's more difficult than writing software itself. It requires a lot of time and energy, and it involves many different skills: writing, coding, knowing how to share and at which intensity. It's a collaborative practice that could open to different voices.
 
 As a piece of code would write: I am documented, therefore I am.