Skip to content

[Documentation] Edit for clarity and style #1534

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 2 commits into from
Apr 25, 2017
Merged

Conversation

jdsandifer
Copy link
Contributor

Around line 143, gave "constants" its own bullet point. Although it is a form of variable or field, it does form a separate style element with a different guideline. It's also easier to find when skimming this way.

Author Checklist:
Changes address original issue? N/A
Unit tests included and/or updated with changes? N/A
Command line build passes? N/A
Changes have been smoke-tested? N/A

Around line 143, gave "constants" its own bullet point. Although it is a form of variable or field, it also forms a separate style element with a different guideline. It's also easier to find when skimming when separated - for new contributors who need to learn the style, and veteran contributors who are just double checking.
@jdsandifer jdsandifer changed the title [Docs] Edit for clarity [Documentation] Edit for clarity Apr 23, 2017
Edited for consistent period and parentheses usage throughout:
 - Removed periods at the end of each element in a list of nouns.
 - Placed periods outside parenthetical statements that aren't complete sentences themselves.
 - Placed periods at the end of sentences without punctuation.
@jdsandifer jdsandifer changed the title [Documentation] Edit for clarity [Documentation] Edit for clarity and style Apr 23, 2017
@VWoeltjen
Copy link
Contributor

Thanks for these changes as well, that does read better. I also realize now that I have for many years had wrong ideas about the correct ordering of terminal punctuation and parentheses (which will take some getting used to).

Reviewer Checklist

  1. Changes appear to address issue? N/A (rationale for changes documented in commit messages)
  2. Appropriate unit tests included? N/A
  3. Code style and in-line documentation are appropriate? Y
  4. Commit messages meet standards? Y

@VWoeltjen VWoeltjen merged commit fd33127 into nasa:master Apr 25, 2017
@jdsandifer jdsandifer deleted the patch-3 branch April 25, 2017 23:46
@jdsandifer
Copy link
Contributor Author

That kind of thing has definitely happened to me before. And I'm always looking up grammar rules because I usually can't remember all the details and exceptions.

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.

2 participants