diff --git a/doc/thesis/buffered_read.tex b/doc/thesis/buffered_read.tex
index a6de1db..a613dff 100644
--- a/doc/thesis/buffered_read.tex
+++ b/doc/thesis/buffered_read.tex
@@ -95,7 +95,7 @@ \subsection{Protocol}
 write connection. This allows us to update the \code{head} accordingly when freeing messages out of order and freeing will
 occasionally update the remote head using an RDMA write operation.
 
-\paragraph{} For both ring-buffers we use the same \emph{"Magic Buffer"} trick introduced in Section~\ref{sec:conn:buf_write} to 
+\paragraph{} For both ring-buffers we use the same \emph{``Magic Buffer"} trick introduced in Section~\ref{sec:conn:buf_write} to 
 allow us to wrap around the end of the buffer.
 
 \subsection{Feature Analysis}
@@ -110,4 +110,4 @@ \subsection{Feature Analysis}
 
 \paragraph{} For future work it would also be interesting to implement a system where multiple threads can write to and receive 
 from a single  connection by atomically updating head or tail pointers, or we could explore the possibilities of sharing send or
-receive buffers using atomic operations. The current implementation, however, does not provide any kind of \emph{Resource Sharing}
+receive buffers using atomic operations. The current implementation, however, does not provide any kind of \emph{Resource Sharing}.
diff --git a/doc/thesis/protocols.tex b/doc/thesis/protocols.tex
index c7283b4..4646ad4 100644
--- a/doc/thesis/protocols.tex
+++ b/doc/thesis/protocols.tex
@@ -38,7 +38,7 @@ \subsection{Features} \label{sec:features}
 a few microseconds.
 
 To be able to better compare our presented protocols, we define a few traits that are often required by systems and
-analyse which protocols provide these traits
+analyse which protocols provide these traits.
 
 \paragraph{True Zero-Copy} A protocol is truly zero copy if it can receive directly to the destination address. While RDMA 
 claims to be zero-copy, most protocols are not truly zero-copy. Protocols using ring-buffers or mailboxes are
@@ -188,7 +188,7 @@ \subsubsection{Read-Based Protocols}
 \paragraph{} A \emph{Unbuffered Read Protocol} avoids the additional copy which is usually necessary when using a buffer. This means the 
 sender needs to notify the receiver when a new message arrives and where to read it from.  This introduces a large
 communication overhead but by being truly zero-copy this approach can be efficient, especially for large messages.
-We present our implementation of an \emph{Unbuffered Read Protocol} in Section~\ref{sec:conn:direct_read}..
+We present our implementation of an \emph{Unbuffered Read Protocol} in Section~\ref{sec:conn:direct_read}.
 
 
 \pagebreak