please don't

more than ok if you improve legibility of specific lines,

but this kind of rewriting put a lot of pressure on we maintainers when we merge from English

Well, @p2635 , I tried to fix both issues here.
Any review/advice from a native Eng speaker would be nice...

Update article.md

change n instead of m

Merge pull request #682 from firedevelop/patch-1

change n instead of m

👍

Update article.md

Merge pull request #677 from javascript-tutorial/EzequielCaste-patch-1

Update article.md

small typo

This PR was automatically generated to merge changes from en.javascript.info at ea7738bb

Conflicted files in this PR have labels ">>>..." with both sides of conflict. If you merge this PR, you'll need to examine the listed files and resolve conflicts.

Alternatively, you can close this PR and merge conflicting changes manually.

The following files have conflicts and may need updates of the translations:

• [ ] 1-js/02-first-steps/10-ifelse/article.md
• [ ] 1-js/05-data-types/05-array-methods/article.md
• [ ] 5-network/10-long-polling/article.md

To merge changes manually (instead of merging this PR):

1. Add remote upstream that links to the English version (only needs to be done once)
   • git add remote upstream https://github.com/javascript-tutorial/en.javascript.info
2. Commit all current work locally and git checkout master
3. Pull the recent changes from the English version:
   • git pull upstream master
4. Deal with the conflicts. If a conflict touches a few lines, then just fix it. Otherwise, following commands can help:
   • Checkout your (translated) version of a file/folder at the given path (removes all upstream changes):
     • git checkout --ours <path>
   • See the diff, what changed in the upstream file since branches diverged:
     • git diff --word-diff master...upstream/master <path> (please note: three dots in the command)
   • Then you can examine the changes in upstream and add them manually
5. When conflicts resolved, commit them and git push origin master

This PR will be closed and replaced with a new one in a few days.

This PR was automatically generated to merge changes from en.javascript.info at 1ce5644a

Conflicted files in this PR have labels ">>>..." with both sides of conflict. If you merge this PR, you'll need to examine the listed files and resolve conflicts.

Alternatively, you can close this PR and merge conflicting changes manually.

The following files have conflicts and may need updates of the translations:

• [ ] 1-js/02-first-steps/10-ifelse/article.md

To merge changes manually (instead of merging this PR):

1. Add remote upstream that links to the English version (only needs to be done once)
   • git add remote upstream https://github.com/javascript-tutorial/en.javascript.info
2. Commit all current work locally and git checkout master
3. Pull the recent changes from the English version:
   • git pull upstream master
4. Deal with the conflicts. If a conflict touches a few lines, then just fix it. Otherwise, following commands can help:
   • Checkout your (translated) version of a file/folder at the given path (removes all upstream changes):
     • git checkout --ours <path>
   • See the diff, what changed in the upstream file since branches diverged:
     • git diff --word-diff master...upstream/master <path> (please note: three dots in the command)
   • Then you can examine the changes in upstream and add them manually
5. When conflicts resolved, commit them and git push origin master

This PR will be closed and replaced with a new one in a few days.

hey bot let s see if you're smart

i won t work until. i feel ok

assigned/ reviewer... me.

yeah im crazy,but good worker goodbyr ro hope see you not toosoon

godspeed

This PR was automatically generated to merge changes from en.javascript.info at 1ce5644a

Conflicted files in this PR have labels ">>>..." with both sides of conflict. If you merge this PR, you'll need to examine the listed files and resolve conflicts.

Alternatively, you can close this PR and merge conflicting changes manually.

The following files have conflicts and may need updates of the translations:

• [ ] 1-js/02-first-steps/10-ifelse/article.md

To merge changes manually (instead of merging this PR):

1. Add remote upstream that links to the English version (only needs to be done once)
   • git add remote upstream https://github.com/javascript-tutorial/en.javascript.info
2. Commit all current work locally and git checkout master
3. Pull the recent changes from the English version:
   • git pull upstream master
4. Deal with the conflicts. If a conflict touches a few lines, then just fix it. Otherwise, following commands can help:
   • Checkout your (translated) version of a file/folder at the given path (removes all upstream changes):
     • git checkout --ours <path>
   • See the diff, what changed in the upstream file since branches diverged:
     • git diff --word-diff master...upstream/master <path> (please note: three dots in the command)
   • Then you can examine the changes in upstream and add them manually
5. When conflicts resolved, commit them and git push origin master

This PR will be closed and replaced with a new one in a few days.

Hey Don Bot, I haven't finished it yet.

again

the engine? or the code.

I'm thinking that the engine interprets the code.

hard to explain... it's about levels of abstraction... can't think better I'll drop it

And I still think the comma is mandatory... :)

about the await, yes, I think the only one needed is called at the top ofthe function

well, this is only browser code, it'll be hard to reach the hard limit

maybe a warning "dont think it is a good idea to code like this in a forever runing node server"

the engine? or the code.