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

typos

Browse source 
o -> on
build-in -> built-in
This commit is contained in:
dragonwocky 2019-04-16 15:16:36 +10:00 • committed by GitHub
parent 8a9d97a7f9
commit 81a37be350
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
1-js/09-classes/06-extend-natives/article.md
View file

@ -1,5 +1,5 @@
# Extending build-in classes
# Extending built-in classes
Built-in classes like Array, Map and others are extendable also.
@ -29,7 +29,7 @@ arr.constructor === PowerArray
```
So when `arr.filter()` is called, it internally creates the new array of results exactly as `new PowerArray`.
That's actually very cool, because we can keep using `PowerArray` methods further o the result.
That's actually very cool, because we can keep using `PowerArray` methods further on the result.
Even more, we can customize that behavior.
@ -73,7 +73,7 @@ And we've already been talking about native classes extending each other: `Array
But statics are an exception. Built-in classes don't inherit static properties from each other.
In other words, the prototype of build-in constructor `Array` does not point to `Object`. This way `Array` and `Date` do not have `Array.keys` or `Date.keys`. And that feels natural.
In other words, the prototype of built-in constructor `Array` does not point to `Object`. This way `Array` and `Date` do not have `Array.keys` or `Date.keys`. And that feels natural.
Here's the picture structure for `Date` and `Object`: