jeena/en.javascript.info
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

"Can" instead of "Can't"

Browse source 
I think that's what the author meant.
This commit is contained in:
Christian Reed 2018-10-23 13:05:47 -07:00 • committed by GitHub
parent dc904d122e
commit afe292b153
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
1-js/05-data-types/02-number/article.md
View file

@ -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. 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 ```js run
alert( parseInt('100px') ); // 100 alert( parseInt('100px') ); // 100