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

Copy edits #20

Merged
merged 4 commits into from
May 14, 2022
Merged

Conversation

sideshowbarker
Copy link
Contributor

@sideshowbarker sideshowbarker commented May 14, 2022

  • Change “discussions between” to “discussions among” 90a2153
  • Lowercase “browser” in “non-Browser” 43ad5a9
  • Write out “JavaScript” rather than “JS” 93e83ca
  • Avoid repeated use of “existing” 97d9013

Each of the changes listed above is a separate commit here — so any of them that are undesired can just be rebased out.

“discussions between” isn’t strictly wrong, but when writing about
discussions involving more than two parties, it’s common practice to use
“discusions among” the parties — and using “discussions between” when
writing about discussions involving just two parties. See the examples
at https://textranch.com/667108/discussion-between/or/discussion-among/

There are exceptions of course — but looking through those examples will
show that general practice is “between” for two-party discussions, and
“among” for more-than-two-parties discussions.
…there’s no reason for “browser” to be uppercase here
Casually-abbreviated “JS” in “JS runtimes” isn’t strictly wrong, but
“JavaScript runtimes” — written out — is better in this context (which
is effectively a standalone mission statement) because it’s completely
clear and unambiguous. Otherwise, since there’s nowhere else any
explicit mention of JavaScript in the page, using just “JS” risks being
less clear to some readers. And as a kind of mission statement, it’s
better for the language here to be a bit more formal and less casual.
Given that the final sentence of this mission statement contains just 28
words, having the word “existing” occur in it 3 times seems like maybe a
couple times too much…
@w3cbot
Copy link

w3cbot commented May 14, 2022

sideshowbarker marked as non substantive for IPR from ash-nazg.

Copy link
Member

@lucacasonato lucacasonato left a comment

Choose a reason for hiding this comment

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

Thanks Michael!

@lucacasonato lucacasonato merged commit 858dbd3 into wintercg:main May 14, 2022
@sideshowbarker sideshowbarker deleted the sideshowbarker/copy-edits branch May 14, 2022 23:13
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.

None yet

3 participants