From f55937c99dfdd08d89d3d7db24780d42b9f4ea75 Mon Sep 17 00:00:00 2001
From: Max-001 <80035972+Max-001@users.noreply.github.com>
Date: Fri, 20 Sep 2024 12:03:16 +0200
Subject: Last minor changes

---
 plan.tex | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/plan.tex b/plan.tex
index 55707ce..c439aa7 100644
--- a/plan.tex
+++ b/plan.tex
@@ -38,18 +38,18 @@ Finally, because the client does not want to dive deeply into the engine himself
 
 \subsection{Goal}
 
-The goal is to develop a custom game engine that meets the client's requirements for maintainability, extensibility, user-friendliness, and adherence to a Unity-like structure. The engine may integrate third-party software (as agreed with the client) to support specific features, such as audio, physics, and rendering. In addition, a validation application is created to show and test the engine's features.
+The goal is to develop a custom game engine that meets the client's requirements for maintainability, extensibility, user-friendliness, and adherence to a Unity-like structure. The engine may integrate third-party software (as agreed with the client) to support specific features, such as audio, physics, and rendering. In addition, a \emph{validation application} is created to show and test the engine's features.
 
 \subsection{Scope}
 The requirements document \autocite{crepe:requirements} has several requirements with a MoSCoW `must', `should', `could' or `won't' priority to indicate the project's scope.
 
 \subsection{Result}
 
-The expected result is a well-documented, custom game engine that follows a structure similar to Unity. Additionally, a validation application should be provided to test and showcase the engine's capabilities.
+The expected result is a well-documented, custom game engine that follows a structure similar to Unity. Additionally, a \emph{validation application} should be provided to test and showcase the engine's capabilities.
 
 \subsection{Validation Application}
 
-The validation application \autocite{crepe:validation-application} is explained in a document where the features of the validation application are linked to the user stories.
+The \emph{validation application} \autocite{crepe:validation-application} is explained in a document where the features of the \emph{validation application} are linked to the user stories.
 
 \section{Planning}
 
@@ -63,7 +63,7 @@ The customer specified multiple deliverables throughout the 20 weeks of this pro
 		4 & Project Plan\\
 		7 & Some POCs\\
 		10 & POCs and Design document\\
-		17 & Game engine, Validation application\\
+		17 & Game engine, \emph{validation application}\\
 		\bottomrule
 	\end{tabularx}
 	\caption{Planning}
@@ -145,7 +145,7 @@ reviewed and agreed to these terms.
 	\item[Loek Le Blansch] Integrator
 	\item[Wouter Boerenkamps] Project Member
 	\item[Jaro Rutjes] Team Leader / Scrum Master
-	\item[Max Smits] Project Member / Product owner
+	\item[Max Smits] Project Member / Product Owner
 	\item[Niels Stunnebrink] Project Member
 \end{description}
 
-- 
cgit v1.2.3