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.

Sign up for GitHub

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

Jump to bottom

Copy edits #20

Merged
merged 4 commits into from
May 14, 2022
Merged

Copy edits #20

merged 4 commits into from
May 14, 2022

Commits on May 14, 2022

  1. Change “discussions between” to “discussions among” 

    “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.
    @sideshowbarker
    sideshowbarker committed May 14, 2022
    Configuration menu
    Copy the full SHA
    90a2153 View commit details
    Browse the repository at this point in the history

  2. Lowercase “browser” in “non-Browser” 

    …there’s no reason for “browser” to be uppercase here
    @sideshowbarker
    sideshowbarker committed May 14, 2022
    Configuration menu
    Copy the full SHA
    43ad5a9 View commit details
    Browse the repository at this point in the history

  3. Write out “JavaScript” rather than “JS” 

    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.
    @sideshowbarker
    sideshowbarker committed May 14, 2022
    Configuration menu
    Copy the full SHA
    93e83ca View commit details
    Browse the repository at this point in the history

  4. Avoid repeated use of “existing” 

    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…
    @sideshowbarker
    sideshowbarker committed May 14, 2022
    Configuration menu
    Copy the full SHA
    97d9013 View commit details
    Browse the repository at this point in the history