Skip to content

Commit 358c389

Browse files
authored
Update article.md
1 parent 5b63e81 commit 358c389

File tree

1 file changed

+2
-2
lines changed
  • 1-js/08-prototypes/01-prototype-inheritance

1 file changed

+2
-2
lines changed

1-js/08-prototypes/01-prototype-inheritance/article.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -133,11 +133,11 @@ Also it may be obvious, but still: there can be only one `[[Prototype]]`. An obj
133133

134134

135135
```smart header="`__proto__` is a historical getter/setter for `[[Prototype]]`"
136-
It's a common mistake of novice developers not to know the difference between these two.
136+
It's a common mistake of novice developers not to know the difference between these two.
137137

138138
Please note that `__proto__` is *not the same* as the internal `[[Prototype]]` property. It's a getter/setter for `[[Prototype]]`. Later we'll see situations where it matters, for now let's just keep it in mind, as we build our understanding of JavaScript language.
139139

140-
The `__proto__` property is a bit outdated. It exists for historical reasons, modern JavaScript suggests that we should use `Object.getPrototypeOf/Object.setPrototypeOf` functions instead that get/set the prototype. We'll also cover these functions later.
140+
The `__proto__` property is a bit outdated. It exists for historical reasons, modern JavaScript suggests that we should use `Object.getPrototypeOf/Object.setPrototypeOf` functions instead that get/set the prototype. We'll also cover these functions later.
141141

142142
By the specification, `__proto__` must only be supported by browsers. In fact though, all environments including server-side support `__proto__`, so we're quite safe using it.
143143

0 commit comments

Comments
 (0)