added some feadback

1 files changed, 28 insertions, 28 deletions

diff --git a/plan.tex b/plan.tex
index 7eea565..69a28ae 100644
--- a/plan.tex
+++ b/plan.tex
@@ -16,27 +16,27 @@ This section describes the required documentation for the project, including the
 
 \subsection{Documents}
 
-This project consists of five main documents:
+This project consists of five main documents:\noparbreak
 
 \begin{description}
 	\item[Project Plan] Contains all elements related to the organization of the
 	 project, including timelines, milestones, roles, responsibilities.
-	\item \textbf{Requirements:} Details the requirements and 
+	\item[Requirements] Details the requirements and 
 	user stories, including both functional and non-functional requirements. 
-	\item \textbf{Research:} Consists of all research related to this project.
-	\item \textbf{Design:} Describes the design choices, including architecture,
+	\item[Research] Consists of all research related to this project.
+	\item[Design] Describes the design choices, including architecture,
 	 user interface, and system components.
-	\item \textbf{Qualification:} Includes test cases, test plans, and quality 
+	\item[Qualification] Includes test cases, test plans, and quality 
 	measures to ensure the project meets its requirements and standards.
-	\item \textbf{Working hours:} 
-	\item \textbf{Api referenece:} 
+	\item[Working hours] 
+	\item[Api referenece]  
 \end{description}
 
-\subsection{Documentation Standard}
+\subsection{Documentation standard}
 
 \newpage
 
-\section{Work Agreements}
+\section{Work agreements}
 Work agreements are the expectations and commitments made by the team members. 
 This section includes details on roles and responsibilities, documentation of 
 work hours, protocols for handling absences or delays, guidelines for addressing
@@ -57,23 +57,23 @@ work hours, protocols for handling absences or delays, guidelines for addressing
 Each project member will keep track of their own working hours and 
 add them to the `file'.
 
-\subsection{Absents or delay}
+\subsection{Absence or delay}
 If a project member is going to be absent or delayed, they are required to 
 notify the team through either WhatsApp or Outlook. Additionally, the teacher 
 should be informed of the absence as well.
 
-\subsection{Inconsistent Participation}
+\subsection{Inconsistent participation}
 Inconsistent participation will be addressed in a structured manner:
 
-\begin{enumerate}
-	\item \textbf{Initial Discussion}: The team leader will first discuss the 
+\begin{description}
+	\item[Initial Discussion] The team leader will first discuss the 
 	issue of inconsistent participation with the individual team member.
-	\item \textbf{Team Discussion}: If no improvement is observed, the issue 
+	\item [Team Discussion]: If no improvement is observed, the issue 
 	will be brought up with the entire team to seek a collective solution.
-	\item \textbf{Project Supervisor Involvement}: Should the problem persist 
+	\item [Project Supervisor Involvement]: Should the problem persist 
 	despite these efforts, it will be escalated to the project supervisor for 
 	further action.
-\end{enumerate}
+\end{description}
 
 Valid reasons for absence or inconsistency will be considered, and no 
 repercussions will be necessary in such cases. However, if the inconsistency is 
@@ -116,22 +116,22 @@ The team will start using scrum after the inital fase of sructering the project
 \subsection{Scrum Board}
 The \href{https://miro.com/app/board/uXjVKjtdM64=/?share_link_id=303851465474}{Scrum board} will consist of the following tabs:
 
-\begin{itemize}
-	\item \textbf{Backlog}: This tab contains a list of all tasks and user stories that are planned for future sprints.
-	\item \textbf{Next Sprint}: This tab includes tasks and user stories that have been selected for the upcoming sprint.
-	\item \textbf{Current Sprint}: This tab displays the tasks and user stories that are actively being worked on in the current sprint.
-	\item \textbf{In Progress}: Tasks that are actively being worked on are moved to this tab.
-	\item \textbf{Review}: Completed tasks that are awaiting review or testing will be placed in this tab.
-	\item \textbf{Done}: Once tasks have been reviewed and are considered complete, they are moved to the Done tab.
-	\item \textbf{Blocked}: This tab is used for tasks that cannot proceed due to obstacles or dependencies.
-\end{itemize}
+\begin{description}
+	\item[Backlog]: This tab contains a list of all tasks and user stories that are planned for future sprints.
+	\item[Next Sprint]: This tab includes tasks and user stories that have been selected for the upcoming sprint.
+	\item[Current Sprint]: This tab displays the tasks and user stories that are actively being worked on in the current sprint.
+	\item[In Progress]: Tasks that are actively being worked on are moved to this tab.
+	\item[Review]: Completed tasks that are awaiting review or testing will be placed in this tab.
+	\item[Done]: Once tasks have been reviewed and are considered complete, they are moved to the Done tab.
+	\item [Blocked]: This tab is used for tasks that cannot proceed due to obstacles or dependencies.
+\end{description}
 
 \noindent
 To manage tasks effectively:
 \begin{itemize}
-	\item A task from the \textbf{Current Sprint} tab should be selected and moved to the \textbf{In Progress} tab when work begins. 
-	\item The status of the task should be updated to \textbf{In Progress} as soon as work starts.
-	\item Once the task is completed and reviewed, it should be moved to the \textbf{Done} tab, and its status should be updated to \textbf{Done}.
+	\item A task from the \emph{Current Sprint} tab should be selected and moved to the \emph{In Progress} tab when work begins. 
+	\item The status of the task should be updated to \emph{In Progress} as soon as work starts.
+	\item Once the task is completed and reviewed, it should be moved to the \emph{Done} tab, and its status should be updated to \emph{Done}.
 \end{itemize}
 
 \noindent