From cf1782ac05318ebf8670664783e81da2802fb2ea Mon Sep 17 00:00:00 2001 From: Alex Hughes Date: Sun, 16 Jul 2017 14:52:11 -0400 Subject: [PATCH] Fixed typo - changed 'no any other value' to 'not' --- 1-js/02-first-steps/08-comparison/article.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/1-js/02-first-steps/08-comparison/article.md b/1-js/02-first-steps/08-comparison/article.md index 61be0e77..7b6b91c5 100644 --- a/1-js/02-first-steps/08-comparison/article.md +++ b/1-js/02-first-steps/08-comparison/article.md @@ -153,7 +153,7 @@ For a strict equality check `===` ``` For a non-strict check `==` -: There's a special rule. These two are a "sweet couple": they equal each other (in the sense of `==`), but no any other value. +: There's a special rule. These two are a "sweet couple": they equal each other (in the sense of `==`), but not any other value. ```js run alert( null == undefined ); // true @@ -162,7 +162,7 @@ For a non-strict check `==` For maths and other comparisons `< > <= >=` : Values `null/undefined` are converted to a number: `null` becomes `0`, while `undefined` becomes `NaN`. -Now let's see funny things that happen when we apply those rules. And, what's more important, how do not fall into a trap with these features. +Now let's see funny things that happen when we apply those rules. And, what's more important, how to not fall into a trap with these features. ### Strange result: null vs 0