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

Merge pull request #887 from srogalsky8/patch-1

Browse source 
Typo in article.md
This commit is contained in:
Ilya Kantor 2019-04-03 09:19:49 +03:00 • committed by GitHub
commit 374bd26393
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

2
1-js/09-classes/01-class-patterns/article.md
View file

@ -7,7 +7,7 @@ In object-oriented programming, a *class* is an extensible program-code-template
There's a special syntax construct and a keyword `class` in JavaScript. But before studying it, we should consider that the term "class" comes from the theory of object-oriented programming. The definition is cited above, and it's language-independent. There's a special syntax construct and a keyword `class` in JavaScript. But before studying it, we should consider that the term "class" comes from the theory of object-oriented programming. The definition is cited above, and it's language-independent.
In JavaScript there are several well-known programming patterns to make classes even without using the `class` keyword. People talk about "classes" meaning no only those defined with `class`, but also with these patterns. In JavaScript there are several well-known programming patterns to make classes even without using the `class` keyword. People talk about "classes" meaning not only those defined with `class`, but also with these patterns.
The `class` construct will be described in the next chapter, but in JavaScript it's a "syntax sugar" and an extension of the prototypal class pattern described here. The `class` construct will be described in the next chapter, but in JavaScript it's a "syntax sugar" and an extension of the prototypal class pattern described here.

2
1-js/13-modules/03-modules-dynamic-imports/article.md
View file

@ -3,7 +3,7 @@
Export and import statements that we covered in previous chaters are called "static". Export and import statements that we covered in previous chaters are called "static".
What's because they are indeed static. The syntax is very strict. That's because they are indeed static. The syntax is very strict.
First, we can't dynamicaly generate any parameters of `import`. First, we can't dynamicaly generate any parameters of `import`.

4
2-ui/1-document/04-searching-elements-dom/article.md
View file

@ -266,8 +266,8 @@ All methods `"getElementsBy*"` return a *live* collection. Such collections alwa
In the example below, there are two scripts. In the example below, there are two scripts.
1. The first one creates a reference to the collection of `<div>`. As of now, it's length is `1`. 1. The first one creates a reference to the collection of `<div>`. As of now, its length is `1`.
2. The second scripts runs after the browser meets one more `<div>`, so it's length is `2`. 2. The second scripts runs after the browser meets one more `<div>`, so its length is `2`.
```html run ```html run
<div>First div</div> <div>First div</div>