Skip to content

Sync with upstream @ 71ff8f81#7

Closed
javascript-translate-bot wants to merge 286 commits intomasterfrom
sync-71ff8f81
Closed

Sync with upstream @ 71ff8f81#7
javascript-translate-bot wants to merge 286 commits intomasterfrom
sync-71ff8f81

Conversation

@javascript-translate-bot

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

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.

Raggan and others added 30 commits August 28, 2019 21:54
So here JavaScript assumes that we have a code block, but why there's an error. --> Makes no sense so replaced "but" with "that's"
Better grammatically.
Wording of initial explanation of spread operator.
1. Since is general statement, thought might be better to use general function name.
2. "Do the following steps" is a bit awkward, in that usually one doesn't "do" steps (but rather "takes", or "follows", or "executes" steps, perhaps). But it does convey the meaning, and perhaps it's a relatively new usage in business or tech that I'm not familiar with. For me, it comes off a bit awkward. Leaving out "steps" works grammatically and preserves the sense. Or could find another verb to replace "do" -- but nothing perfect came to mind. Not that bad the way it is, but since I was already changing the sentence...
Says "is the same object as:", but what's below is an assignment (that includes an object). I didn't have any problem understanding it, didn't even notice it at first, but I thought it would be more accurate this way without sacrificing clarity.
Qualify that while cachingDecorator() will now work with any number of arguments, the hash() function given will not. Or, perhaps better, could just change the hash function to something like:

function hash(args) {
  return [...args].join();
}
dashaezhova and others added 25 commits October 2, 2019 15:32
Replace 'cause' with 'case'.
Update article.md
Minor grammar fixes
Update article.md
Give results of 'alert' ('true') rather than description of method. Code seems pretty self-explanatory.
Replaced 'the ... property ... works since" with "the ... property ... has worked since".
Replaced ":"s with ","s. 

I edited these lines before, and thought they were a little awkward w/ ":"s, but didn't see fit to change it then. But now ","s seem clearly better. Think of it as successive approximations.
[Fetch: Cross-Origin Requests] Fix grammatical errors
Add results of 2nd alert
object constructor -> the object's constructor
'chapter' -> 'article'
Remove unnecessary code syntax inside buttons
@CLAassistant
Copy link

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 9 committers have signed the CLA.

✅ iliakan
✅ Violet-Bora-Lee
❌ paroche
❌ dashaezhova
❌ Oshchenkov
❌ scott-ln
❌ lex111
❌ anuragbhd
❌ ikeq
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.