diff --git a/scope-closures/ch1.md b/scope-closures/ch1.md
index 1eb7ec4bf..bc991ecde 100644
--- a/scope-closures/ch1.md
+++ b/scope-closures/ch1.md
@@ -162,7 +162,7 @@ It's hard to imagine a production-quality JS engine going to all the trouble of
 
 Many have endeavored to split hairs with this terminology, as there's plenty of nuance and "well, actually..." interjections floating around. But in spirit and in practice, what the engine is doing in processing JS programs is **much more alike compilation** than not.
 
-Classifying JS as a compiled language is not concerned with the distribution model for its binary (or byte-code) executable representations, but rather in keeping a clear distinction in our minds about the phase where JS code is processed and analyzed; this phase observably and indisputedly happens *before* the code starts to be executed.
+Classifying JS as a compiled language is not concerned with the distribution model for its binary (or byte-code) executable representations, but rather in keeping a clear distinction in our minds about the phase where JS code is processed and analyzed; this phase observably and indisputably happens *before* the code starts to be executed.
 
 We need proper mental models of how the JS engine treats our code if we want to understand JS and scope effectively.