From 7aa8d0d07e49fd51688adc9e0216129687f4a944 Mon Sep 17 00:00:00 2001
From: Thomas Forgione <thomas@forgione.fr>
Date: Tue, 29 Oct 2019 15:29:09 +0100
Subject: [PATCH 1/2] THANK YOU MATTPIZ FOR THE MISTAKE

---
 src/foreword/implementation.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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}.
 

From 8767ee4c5ff6421b097c0bf28deb2ba69d13c74e Mon Sep 17 00:00:00 2001
From: Thomas Forgione <thomas@forgione.fr>
Date: Tue, 29 Oct 2019 17:10:08 +0100
Subject: [PATCH 2/2] Improve bib

---
 src/bib.bib | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/src/bib.bib b/src/bib.bib
index 292c5ea..d9f0456 100644
--- a/src/bib.bib
+++ b/src/bib.bib
@@ -468,30 +468,30 @@
 }
 
 @misc{so-survey-2016,
-    title = {Developer Survey Results 2016},
+    title = {Stack Overflow Developer Survey Results},
     year = {2016},
-    author = {Stack Overflow},
+    author = {},
     howpublished = {\url{https://insights.stackoverflow.com/survey/2016#technology-most-loved-dreaded-and-wanted}}
 }
 
 @misc{so-survey-2017,
-    title = {Developer Survey Results 2017},
+    title = {Stack Overflow Developer Survey Results},
     year = {2017},
-    author = {Stack Overflow},
+    author = {},
     howpublished = {\url{https://insights.stackoverflow.com/survey/2017#technology-most-loved-dreaded-and-wanted}}
 }
 
 @misc{so-survey-2018,
-    title = {Developer Survey Results 2018},
+    title = {Stack Overflow Developer Survey Results},
     year = {2018},
-    author = {Stack Overflow},
+    author = {},
     howpublished = {\url{https://insights.stackoverflow.com/survey/2018#technology-most-loved-dreaded-and-wanted}}
 }
 
 @misc{so-survey-2019,
-    title = {Developer Survey Results 2019},
+    title = {Stack Overflow Developer Survey Results},
     year = {2019},
-    author = {Stack Overflow},
+    author = {},
     howpublished = {\url{https://insights.stackoverflow.com/survey/2019#technology-most-loved-dreaded-and-wanted}}
 }