From 6853f6ab78b74274f37d034187dcf68c98ffaf9a Mon Sep 17 00:00:00 2001 From: Shubham <7660565+shubham08gupta@users.noreply.github.com> Date: Tue, 5 May 2020 19:01:06 +0900 Subject: [PATCH] remove duplicate words --- 1-js/04-object-basics/01-object/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/1-js/04-object-basics/01-object/article.md b/1-js/04-object-basics/01-object/article.md index 8d1c7e73..513f2f3e 100644 --- a/1-js/04-object-basics/01-object/article.md +++ b/1-js/04-object-basics/01-object/article.md @@ -360,7 +360,7 @@ alert( *!*key*/!* in user ); // true, property "age" exists Why does the `in` operator exist? Isn't it enough to compare against `undefined`? -Well, most of the time the comparison with `undefined` works fine. But there's But there's a special case when it fails, but `"in"` works correctly. +Well, most of the time the comparison with `undefined` works fine. But there's a special case when it fails, but `"in"` works correctly. It's when an object property exists, but stores `undefined`: