diff --git a/bachelor-project-nikolaj.pdf b/bachelor-project-nikolaj.pdf
index d2cab21..acf7a13 100644
Binary files a/bachelor-project-nikolaj.pdf and b/bachelor-project-nikolaj.pdf differ
diff --git a/bachelor-project-nikolaj.tex b/bachelor-project-nikolaj.tex
index 4c30a9a..1bc6260 100644
--- a/bachelor-project-nikolaj.tex
+++ b/bachelor-project-nikolaj.tex
@@ -265,7 +265,7 @@
 
     The method will be slower, since writing to storage takes longer than keeping the data in memory, but I have decided that the positives outweigh the negatives.
 
-    \subsubsection{Data Type Agnosticism}
+    \subsection{Data Type Agnosticism}
     An important aspect to consider in the functioning of the network monitor is its data type agnosticism: the network monitor does not impose restrictions or perform checks on the type of incoming data. While this approach enhances the speed and simplicity of the implementation, it also places a certain level of responsibility on the recipes that work with the incoming data. The recipes, being responsible for defining the actions taken upon execution of a job, must be designed with a full understanding of this versatility. They should incorporate necessary checks and handle potential inconsistencies or anomalies that might arise from diverse types of incoming data.
 
     \subsection{Testing}