diff --git a/content/Section 6 - Critical Interventions Through Bots (exercise)/2-materiality-of-bots.md b/content/Section 6 - Critical Interventions Through Bots (exercise)/2-materiality-of-bots.md
index a6297c7..282261f 100644
--- a/content/Section 6 - Critical Interventions Through Bots (exercise)/2-materiality-of-bots.md	
+++ b/content/Section 6 - Critical Interventions Through Bots (exercise)/2-materiality-of-bots.md	
@@ -11,10 +11,14 @@ To unpack the materiality of bots, we can have a closer look at three features o
 2. API's
 3. background processes
 
+### Code
+
 The first feature will not come as a surprise: **code**. If we look at the digital materiality of a bot, we can say that it is a script: an executable file that sits on your computer or on a server. Code is used to describe how the bot makes a connection, what behaviour it has and when it comes into action.
 
 There are a whole range of programming languages that a bot-maker can use to make a bot. The most popular ones are Python and Javascript. The choice for a specific language is often based on the preference of the programmer, it is a bit like picking your favorite flavour. However, the choice for a programming language can also be based on the availability of a library around an API. 
 
+### API's
+
 If we talk about the relationship between platform and bots, we cannot escape talking about the **API**. 
 
 The term *API* is an acronym for Application Programming Interface. It is an code-based interface between the programmer and a platform, such as Wikipedia, Reddit, Whatsapp, Twitter or Mastodon. Not all platforms have an API, it's a decision of the owner of the platform to make one. Every API is therfor different and comes with different constraints or rules.
@@ -29,6 +33,8 @@ Essentially does the API determine how the platform developers imagine it will b
 
 So to sum up: a bot is written in code and uses an API to connect to an infrastructure.
 
+### Background processes
+
 In order to run the bot, we need one more last feature: a so called **process**.
 
 A *process* is nothing more then a term to refer to the act of putting the bot into action. In the most simple version, this can be done by running a script from your own computer. In a more complex version, you could upload your script to a server and run it from there *continuously*.