gaspersic/freeCodeCamp
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Minor typo fix (#23059)

Browse Source
This commit is contained in:
kViking
2018-11-11 18:25:32 -08:00
committed by Aditya
parent ad5062d3ea
commit dc8049df43
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
guide/english/javascript/comparison-operators/index.md
View File

@ -163,7 +163,7 @@ How? This is because there is a special rule for "null" and "undefined". Due to
If we use comparison operators like <, >, <=, >= etc., "null" and "undefined" are converted to number and in such cases "null" will become 0 and "undefined" will be NaN. Lets check some of those examples.
#### Example - compare null with 0(zero)
#### Example - compare null with 0 (zero)
```javascript
console.log( null > 0 ); // O/P - false
@ -177,7 +177,7 @@ The reason is "comparison" and "equality check" both works in different way.
In comparison, "null/undefined" is first converted to number so, in first two cases "null" become 0 and hence case1) (null > 0) -> false and case2) (null >= 0) -> true.
But, in equality check (==), "null/undefined" works without any conversion and as explained above (special rule), in equality check "null/undefined" are only equal to each other and are not equal to anything else. Hence (null == 0) -> false.
#### Example - compare undefined with 0(zero)
#### Example - compare undefined with 0 (zero)
```javascript
console.log( undefined > 0 ); // O/P - false