\section{Requirements}
-The requirements are is ordered following the MoSCoW prioritization method. The
-MoSCoW approach originated from the RAD methodology~\cite{clegg_case_1994}.
-MoSCoW is used to sort the MarsRover features into priority order based on the
-importance. In this way, the developers are able to understand what feature is
-essential to be done. The term MoSCoW itself is an acronym derived from the
-first letter of each of four prioritization categories (Must have, Should have,
-Could have, and Would like but won't get). The first letters are used in the
-first column of \autoref{tab:req} to describe the priority of the requirements.
+\subsection{\emph{MoSCoW}}
+The requirements are ordered following the \emph{MoSCoW} prioritization method.
+The \emph{MoSCoW} approach originated from the RAD
+methodology~\cite{clegg_case_1994}. \emph{MoSCoW} is used to sort the features
+into priority order based on the importance. In this way, the developers are
+able to understand what feature is essential to be done. The term \emph{MoSCoW}
+itself is an acronym derived from the first letter of each of four
+prioritization categories (Must have, Should have, Could have, and Would like
+but will not get). The first letters are used in the first column of
+\autoref{tab:req} to describe the priority of the requirements.
+\subsection{Requirements}
\begin{longtabu}to \linewidth{llX}
\toprule
\rowfont\bfseries Code & Priority & Description\\
\midrule\midrule
\multicolumn{3}{l}{Non-functional requirements}\\
+ \midrule\midrule
NR1 & \textsc{M} & The code should be generated by a DSL.\\
NR2 & \textsc{S} & Finish the entire mission set within the
demonstration time.\\