diff --git a/manuscrit/20_foundations/20_code_analyzers.tex b/manuscrit/20_foundations/20_code_analyzers.tex
index 99831f1..4abe524 100644
--- a/manuscrit/20_foundations/20_code_analyzers.tex
+++ b/manuscrit/20_foundations/20_code_analyzers.tex
@@ -89,9 +89,9 @@ point towards the resources that are limiting the kernel's performance, or
 
 \paragraph{Static vs.\ dynamic analyzers.} Tools analyzing code, and code
 analyzers among them, are generally either performing \emph{static} or
-\emph{dynamic} analyses. Static analysers work on the program itself, be it
+\emph{dynamic} analyses. Static analyzers work on the program itself, be it
 source code, assembly or any representation, without running it; while dynamic
-analysers run the analyzed program, keeping it under scrutiny through either
+analyzers run the analyzed program, keeping it under scrutiny through either
 instrumentation, monitoring or any relevant technique. Some analyzers mix both
 strategies to further refine their analyses. As a general rule of thumb,
 dynamic analyzers are typically more accurate, being able to study the actual