From 86ed165f1b697f3876c57973887d92ccfd7faa17 Mon Sep 17 00:00:00 2001
From: digital-bw <113027504+digital-bw@users.noreply.github.com>
Date: Sat, 24 Sep 2022 19:50:06 +0600
Subject: [PATCH] grammar suggestion

contextually 'true' can be confusing after 'false' in sentence: "... false, technically that's true ..."
---
 1-js/05-data-types/02-number/article.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/1-js/05-data-types/02-number/article.md b/1-js/05-data-types/02-number/article.md
index 8e130f74..0f0ee2bf 100644
--- a/1-js/05-data-types/02-number/article.md
+++ b/1-js/05-data-types/02-number/article.md
@@ -367,7 +367,7 @@ In a way, `Number.isNaN` and `Number.isFinite` are simpler and more straightforw
 There is a special built-in method `Object.is` that compares values like `===`, but is more reliable for two edge cases:
 
 1. It works with `NaN`: `Object.is(NaN, NaN) === true`, that's a good thing.
-2. Values `0` and `-0` are different: `Object.is(0, -0) === false`, technically that's true, because internally the number has a sign bit that may be different even if all other bits are zeroes.
+2. Values `0` and `-0` are different: `Object.is(0, -0) === false`, technically that's correct, because internally the number has a sign bit that may be different even if all other bits are zeroes.
 
 In all other cases, `Object.is(a, b)` is the same as `a === b`.