From b536ce1eb8b6eadf8b0a212334fd8a736011b3fe Mon Sep 17 00:00:00 2001 From: Carl Smith Date: Fri, 17 Aug 2018 14:05:46 -0400 Subject: [PATCH] Corrected incomplete sentence in "Comparisons" page --- 1-js/02-first-steps/08-comparison/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/1-js/02-first-steps/08-comparison/article.md b/1-js/02-first-steps/08-comparison/article.md index 00ae53f1..6a69c95e 100644 --- a/1-js/02-first-steps/08-comparison/article.md +++ b/1-js/02-first-steps/08-comparison/article.md @@ -176,7 +176,7 @@ Yeah, mathematically that's strange. The last result states that "`null` is grea The reason is that an equality check `==` and comparisons `> < >= <=` work differently. Comparisons convert `null` to a number, hence treat it as `0`. That's why (3) `null >= 0` is true and (1) `null > 0` is false. -On the other hand, the equality check `==` for `undefined` and `null` works by the rule, without any conversions. They equal each other and don't equal anything else. That's why (2) `null == 0` is false. +On the other hand, the equality check `==` for `undefined` and `null` is defined such that, without any conversions, they equal each other and don't equal anything else. That's why (2) `null == 0` is false. ### An incomparable undefined