diff --git a/src/foreword/implementation.tex b/src/foreword/implementation.tex
index c74f69c..dd5ff87 100644
--- a/src/foreword/implementation.tex
+++ b/src/foreword/implementation.tex
@@ -113,7 +113,7 @@ And effectively, the borrow checker will crash the compiler with the error in Li
 \end{figure}
 
 This example is one of the many examples of how powerful the borrow checker is: in Rust code, there can be no dangling reference, and all the segmentation faults coming from them are detected by the compiler.
-The borrow checker may seem like an enemy to newcomers because it often rejects code that seem correct, but once one get used to it, they understand what is the problem with their code and either fix the problem easily, or realise that the whole architecture is wrong and understand why.
+The borrow checker may seem like an enemy to newcomers because it often rejects code that seem correct, but once one gets used to it, they understand what is the problem with their code and either fix the problem easily, or realise that the whole architecture is wrong and understand why.
 
 It is probably for those reasons that Rust is the \emph{most loved programming language} according to the Stack Overflow Developer Survey in~\citeyear{so-survey-2016,so-survey-2017,so-survey-2018} and~\citeyear{so-survey-2019}.