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

Proof-reading of "So Whats Next" #1186

Merged
merged 9 commits into from
Feb 23, 2023
Merged

Conversation

Luashine
Copy link
Contributor

@Luashine Luashine commented Feb 15, 2023

I was pretty liberal in my edits, tried to understand author's intentional words and rephrase them better in some places.

@rybak just notified me that he on it as well at the moment, but I'm creating this PR and calling it a day (or night) ;) Overall I'm surprised that only 3 people decided to help so far... Or am I? 🎶


TODO:

  1. + Merge rybak's PR
  2. - Revise the donation paragraph
  3. - Discuss and commit tonight's (19.02.) fixes
  4. ? Native speakers are welcome to comment about further mistakes

Discussed and implemented already:

EDIT: Так, остались записки в блокноте:

line 196: "это + и это" будет корректнее перевести (как минимум) как It is, если не усложнять и не дописывать предложения.

На заметку: Тире в таком количестве не используются в других языках, они, скорее, атипичны. Больше запятых, простых предложений, акцента посредством двоеточий.

L466 However, there are always options and there would be a desire.

Как предложение по-русски, особенно часть про desire? Если конструкция "было бы желание", то надо переписать предложение.

L14 but sometimes this is the most of JS standard library that they use.

"the most of" тут о чем?

На L56 специально добавила символ процента, для наглядности.

rybak and others added 6 commits February 14, 2023 23:09
Some places in post "2023-02-14-so-whats-next.md" use spaced hyphens,
some use spaced m-dashes.  Replace usages of spaced hyphen (-) with more
appropriate m-dash (—) for consistency and readability.
The post "2023-02-14-so-whats-next.md" uses a combination of straight
double quotes ("") and curly double quotes (“”).  Replace the only usage
of curly ones with straight double quotes.
The post "2023-02-14-so-whats-next.md" uses a combination of straight
single quotes (') and curly single quotes (’).  Replace all usages of
curly ones with straight single quotes.
Fix wording in 2023-02-14-so-whats-next.md: add missing words, replace
words, rearrange sentences, etc.
I was pretty liberal in my edits, tried to understand author's
intentional words and rephrase them better in some places.
@Luashine Luashine changed the title [CI-SKIP] Proof-reading of "So Whats Next" Proof-reading of "So Whats Next" Feb 15, 2023
Copy link
Contributor

@rybak rybak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

First of all, thank you for the PR. I don't have bandwidth right now to look through the changes, but I noticed that you've updated only file docs/2023-02-14-so-whats-next.md. At the moment the same content is included in README.md, which should be updated as well.

@zloirock
Copy link
Owner

Thanks. I'm in the hospital all this day for a checkup, so I'll check it later.

Changes up to 23:28, excluding the donations chapter
… rybak/grammar-fixes

Since this is a natural text with multiple options, this merge commit
actually changes some sentences to accomodate both suggestions.

The dash changes were kept where possible.
The single- and double-quote changes were not respected during merge,
because I did not read Rybak's commit messages; they're indeed
inconsistent.
Fix up after the previous merge.
This includes the left over m-dash, single quotes, double-quotes.
@zloirock
Copy link
Owner

(CI fails because of Node 19.7 bug, nodejs/node#46755)

@zloirock zloirock merged commit eab5a48 into zloirock:master Feb 23, 2023
@zloirock
Copy link
Owner

Thanks a lot -)

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

Successfully merging this pull request may close these issues.

3 participants