From 0d35af590936e9e2a327d5146a3b828c95aa1657 Mon Sep 17 00:00:00 2001 From: Bryon Larrance Date: Tue, 27 Jun 2017 15:41:45 -0500 Subject: [PATCH] Typo Typo in parseInt section. --- 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 ff07c661..0f08860d 100644 --- a/1-js/05-data-types/02-number/article.md +++ b/1-js/05-data-types/02-number/article.md @@ -362,7 +362,7 @@ alert( parseFloat('12.3.4') ); // 12.3, the second point stops the reading Of course, there are situations when `parseInt/parseFloat` return `NaN`. It happens when no digits could be read: ```js run -alert( parseInt('a123') ); // NaN, the first symbol stops he process +alert( parseInt('a123') ); // NaN, the first symbol stops the process ``` ````smart header="The second argument of `parseInt(str, radix)`"