type_analysis: fix a few typos

Author: mewmew

report/type_analysis/inc/ssa.c

@@ -3,8 +3,10 @@ int f(int a) {
 	switch (a) {
 	case 5:
 		x = a * 2;
+		break;
 	default:
 		x = a * 3;
+		break;
 	}
 	return x;
 }

report/type_analysis/sections/2_background/2_type_lattice.tex

@@ -9,7 +9,7 @@ \subsection{Type Lattice}
 	\item $\bot$: inconsistent type
 \end{itemize}
 
-In the type primitive type lattice of TIE (see figure \ref{fig:primitive_type_lattice}) for instance, both signed and unsigned 32-bit integers (\texttt{int32} and \texttt{uint32}, respectively) are subtypes of 32-bit integers (\texttt{num32}) \cite{tie_reverse_engineering_of_types}.
+In the primitive type lattice of TIE (see figure \ref{fig:primitive_type_lattice}) for instance, both signed and unsigned 32-bit integers (\texttt{int32} and \texttt{uint32}, respectively) are subtypes of 32-bit integers (\texttt{num32}) \cite{tie_reverse_engineering_of_types}.
 
 \begin{figure}[htbp]
 	\centering

report/type_analysis/sections/3_variable_recovery.tex

@@ -3,7 +3,7 @@
 \section{Variable Recovery}
 \label{sec:variable_recovery}
 
-Variable and typing information is lost during the process of compilation, as local and global variables, function arguments and function parameters are lowered from source code to machine code and mapped onto type-less registers and memory locations. Debug information of binary executables may record this mapping. When debug information is limited or absent however, the source variables have to be recovered from low-level code using variable recovery methods. Since type analysis is based on inference between type typing relations of variables, variable recovery is required for type recovery.
+Variable and typing information is lost during the process of compilation, as local and global variables, function arguments and function parameters are lowered from source code to machine code and mapped onto type-less registers and memory locations. Debug information of binary executables may record this mapping. When debug information is limited or absent however, the source variables have to be recovered from low-level code using variable recovery methods. Since type analysis is based on inference between the typing relations of variables, variable recovery is required for type recovery.
 
 % === [ Subsections ] ==========================================================