Skip to content

Proofread pass of the articles #393

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

Merged
merged 32 commits into from
May 13, 2024
Merged

Proofread pass of the articles #393

merged 32 commits into from
May 13, 2024

Conversation

chuckdude
Copy link
Contributor

Made a proofreading pass through the articles.

Motivation:

To verify there are no typos.

Modifications:

Largely, made edits to correct tense and turn text like "it is" or "does not" into contractions ("it's" and "doesn't", respectively).

Result:

Clean up pass for initial release.

Checklist:

  • Code and documentation should follow the style of the Style Guide.
  • If public symbols are renamed or modified, DocC references should be updated.

@chuckdude chuckdude self-assigned this May 1, 2024
@chuckdude chuckdude added the documentation 📚 Improvements or additions to documentation label May 1, 2024
@@ -61,7 +61,7 @@ The following language comment styles are supported:
Test comments which are automatically added from source code comments preserve
their original formatting, including any prefixes like `//` or `/**`. This
is because the whitespace and formatting of comments can be meaningful in some
circumstances or aid in understanding the commentfor example, when a comment
circumstances or aid in understanding the comment; for example, when a comment
Copy link
Contributor

Choose a reason for hiding this comment

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

A semi-colon is not correct here.

- The strings `"red"`, `"orange"`, `"yellow"`, `"green"`, `"blue"`, or
`"purple"`, representing corresponding predefined instances of ``Tag``, i.e.
- The strings `red`, `orange`, `yellow`, `green`, `blue`, or
`purple`, represent corresponding predefined instances of ``Tag``, like
Copy link
Contributor

Choose a reason for hiding this comment

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

We're not saying "The strings [...] represent", we're saying "The strings—and by the way, they represent". Compare the other cases in this list.


For example, to set the color of the tag `"critical"` to orange and the color of
the tag `.legallyRequired` to teal, the contents of `"tag-colors.json"` can
For example, to set the color of the `critical` tag to orange and the color of
Copy link
Contributor

Choose a reason for hiding this comment

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

critical here is a string literal and needs the quotes.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will revert.

the color in a device-independent RGB color space; or
- The `null` literal value, representing "no color."
``Tag/purple``.
- A string of the form `#RRGGBB`, containing a hexadecimal representation of
Copy link
Contributor

Choose a reason for hiding this comment

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

This is a string literal and needs the quotes.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will revert.

chuckdude and others added 11 commits May 6, 2024 15:47
Changed asterisks back to underscores for italic.
Changed asterisks back to underscores for italics.

Co-authored-by: Jonathan Grynspan <jgrynspan@apple.com>
Put back the quotation marks, and reverted back to representing.
Copy link
Contributor Author

@chuckdude chuckdude left a comment

Choose a reason for hiding this comment

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

Committed the changes from Jonathan's feedback.

chuckdude and others added 5 commits May 6, 2024 15:53
This is correct; thanks for catching this.

Co-authored-by: Jonathan Grynspan <jgrynspan@apple.com>
Fixed, per Jonathan's recommendation.
Copy link
Contributor Author

@chuckdude chuckdude left a comment

Choose a reason for hiding this comment

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

Committed more changes, and a comment about em-dashes.

Copy link
Contributor Author

@chuckdude chuckdude left a comment

Choose a reason for hiding this comment

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

Reviewed all changes. This looks ready to merge.

I think we can eliminate the “Kinds of relationship” heading here, and just make this a continuous part of the higher level section.
@medreisbach medreisbach merged commit 9c31ad5 into main May 13, 2024
@medreisbach medreisbach deleted the chuck/edit-119730853 branch May 13, 2024 20:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation 📚 Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants