Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sync with upstream @ 9acc1302 #9

Closed
wants to merge 23 commits into from

Conversation

javascript-translate-bot

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

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:

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.

lex111 and others added 23 commits February 10, 2020 18:29
It literally says «Operating System system functions.»
add semicolon at end -> "    return prop >= target.start && prop <= target.end;"
"return `undefined`" -> "returns `undefined`"
"on the paper" -> "on paper"
According to the MDN precedence-table you've linked some precedence numbers are incorrect. Having a quick look at different language versions (French and Russian) this error may has to be corrected at every version.
"chapter" -> "article" 2x
"returns to event loop" -> "returns to the event loop"
"no much difference" -> "not much difference"
"move the scheduling to the beginning" (2x)
"similar stuff to described above" -> "similar stuff to what's described above"
"roll our own" -> "roll your own"
"can see that's" - "can see that that's"
Incorrect precedence numbers (prob. "language-wide")
"big text" -> "large amount of text"
"evade problems" -> "avoid problems"
"another 100 lines" -> "for the next 100 lines"
"To demonstrate the approach" -> "To demonstrate this approach"
"instead of syntax-highlighting" -> "instead of text-highlighting,"
"using nested `setTimeout`:" -> "using nested `setTimeout` calls:"
'The browser may even show "the script..." warning' -> 'The browser may even show a "the script..." warning'
"to react on other user actions" -> "to react to other user actions"  (a little more natural sounding)
"From one hand" -> "On one hand"
"get in details" -> "get in to the details"
"if arguments count" -> "if the arguments count"
"allows to easily" -> "allows us to easily"
"seen in the logging example:" -> "seen in the logging example,"
rephrasing rest of above sentence for readability
@claassistantio
Copy link

claassistantio commented Feb 17, 2020

CLA assistant check
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
2 out of 4 committers have signed the CLA.

✅ u-n-known
✅ iliakan
❌ lex111
❌ paroche
You have signed the CLA already but the status is still pending? Let us recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants