diff --git a/bachelor-project-nikolaj.pdf b/bachelor-project-nikolaj.pdf
index 1f4c50d..ed0be10 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 055d2e9..ad40f18 100644
--- a/bachelor-project-nikolaj.tex
+++ b/bachelor-project-nikolaj.tex
@@ -58,11 +58,11 @@
 
     Finally, extending MEOW's event-based scheduler to support network event triggers would enable the simple and efficient exchange of data between workflows running on different machines. This feature is particularly valuable in distributed computing environments, where data processing tasks are often split across multiple systems to maximize resource utilization and minimize latency. By leveraging network event triggers, MEOW would be better equipped to manage complex workflows in these environments, ensuring seamless integration and streamlined data processing
 
-    One specific example of a use-case where network event triggers could prove useful is the workflow for The Brain Imaging Data Structure (BIDS). The BIDS workflow requires data to be sent between multiple machines and validated by a user. Network event triggers could streamline this process by automatically initiating data transfer tasks when specific conditions are met, thereby reducing the need for manual management. Additionally, network triggers could facilitate user validation by allowing users to manually prompt the continuation of the workflow through specific network requests, simplifying the user's role in the validation process
+    One specific example of a use-case where network event triggers could prove useful is the workflow for The Brain Imaging Data Structure (BIDS). The BIDS workflow requires data to be sent between multiple machines and validated by a user. Network event triggers could streamline this process by automatically initiating data transfer tasks when specific conditions are met, thereby reducing the need for manual management. Additionally, network triggers could facilitate user validation by allowing users to manually prompt the continuation of the workflow through specific network requests, simplifying the user's role in the validation process.
 
     \begin{figure}[H]
         \begin{center}
-            \includegraphics[width=0.5\textwidth]{src/BIDS.png}
+            \includegraphics[width=0.6\textwidth]{src/BIDS.png}
         \end{center}
         \caption{\textbf{Temp graph. Replace.} The structure of the BIDS workflow.}
     \end{figure}
@@ -123,13 +123,14 @@
             \item Experiments with triggering on packet \begin{itemize}
                 \item Removes the ability to send arbitrary data
             \end{itemize}
+            \item To simplify, raw data is expected
         \end{itemize}
     \end{tcolorbox}
 
     \subsection{Integrating it into the existing codebase}
 
     \begin{tcolorbox}[colback=lightgray!30!white]
-        Reusing file event triggering by way of temp files.
+        Reusing the system for file event triggering by way of temp files.
     \end{tcolorbox}
     \subsection{Testing}