From afe292b1535c014e8b490c33628a27508bc683dc Mon Sep 17 00:00:00 2001 From: Christian Reed Date: Tue, 23 Oct 2018 13:05:47 -0700 Subject: [PATCH] "Can" instead of "Can't" I think that's what the author meant. --- 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 b42e9f1e..2a5a371e 100644 --- a/1-js/05-data-types/02-number/article.md +++ b/1-js/05-data-types/02-number/article.md @@ -349,7 +349,7 @@ But in real life we often have values in units, like `"100px"` or `"12pt"` in CS That's what `parseInt` and `parseFloat` are for. -They "read" a number from a string until they can. In case of an error, the gathered number is returned. The function `parseInt` returns an integer, whilst `parseFloat` will return a floating-point number: +They "read" a number from a string until they can't. In case of an error, the gathered number is returned. The function `parseInt` returns an integer, whilst `parseFloat` will return a floating-point number: ```js run alert( parseInt('100px') ); // 100