diff --git a/chapters/systemDesign.tex b/chapters/systemDesign.tex
index e8c18368da2cc736764f4cbf67f40f93c5cbd720..454457930cf5a8e3f996e6993b9220d9cd6395dc 100644
--- a/chapters/systemDesign.tex
+++ b/chapters/systemDesign.tex
@@ -1,19 +1,21 @@
+	\subsection{Code of Conduct}
+		The code follows a simple code of conduct. This generally helps avoid variable naming collisions and other issues which may result in undefined behavior.
+		
+	\subsection{Static Design}
+		\subsubsection{Class Diagram}
+			\begin{figure}[H]
+				\centering
+				\includegraphics[width=\textwidth]{Pictures/uml}
+			\end{figure}
+		
+		\subsubsection{Module Diagram}
+			\begin{figure}[H]
+				\centering
+				\caption{System module diagram}
+				\includegraphics[width=\textwidth]{Pictures/componentchart_2}
+			\end{figure}
 
-
-    \subsection{Static Design}
-        \subsubsection{Class Diagram}
-        \begin{figure}[H]
-                \centering
-                \includegraphics[width=\textwidth]{Pictures/uml}
-            \end{figure}
-        \subsubsection{Module Diagram}
-        \begin{figure}[H]
-                \centering
-                \includegraphics[width=\textwidth]{Pictures/componentchart_2}
-            \caption{System module diagram}
-            \end{figure}
-
-    \subsection{Dynamic Design}
-        \subsubsection{Activity Diagram}
-        \subsubsection{Sequence Diagram}
-        \subsubsection{State Diagram}
\ No newline at end of file
+	\subsection{Dynamic Design}
+		\subsubsection{Activity Diagram}
+		\subsubsection{Sequence Diagram}
+		\subsubsection{State Diagram}
\ No newline at end of file
diff --git a/implementation/flightcontroller_imp.tex b/implementation/flightcontroller_imp.tex
index ed5dd4b889f66b2152e9f910bdd1c31472992e7c..b07f85b20e0cd07c79670ed1aa722d63f21ca5b9 100644
--- a/implementation/flightcontroller_imp.tex
+++ b/implementation/flightcontroller_imp.tex
@@ -18,7 +18,9 @@ To be able to do this we need to interact with the flight controller from our MC
 
 The flight controller do have support for four different communication protocols.
 It can take PWM inputs, where one PWM controls one channel.
+%It has
 It have PPM support, which is quite the same as a PWM but it has support for 8 PWM signals on one line.
+%does?
 It do support sBUS, which is some sort of secure serial protocol with inverted signals.
 The last protocol it supports is called MSP (MultiWii Serial Protocol), which also is a serial protocol.
 Our first thought was that we wanted to implement both the MSP and PPM protocols to control the copter.