-
Notifications
You must be signed in to change notification settings - Fork 180
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
Removed future tense from docs content #6646
Conversation
c326a36
to
2154d6a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah! This is a great change. It is pithier and easier to understand.
Native English speakers do not realize how many tenses the English language has.
https://www.myenglishpages.com/english/grammar-lesson-how-many-tenses-are-there-in-english.php
2154d6a
to
e00d315
Compare
build now |
Internal build has been started, your results will be available at build completion. |
Build SUCCESS See the job results in legacy Jenkins UI or in Blue Ocean UI. |
* removed future tense from docs content * removed future tense from developing docs * removed future tense from integrating docs * removed future tense from introduction docs * removed future tense from managing docs * removed future tense from metadata reference docs * removed future tense from quick start docs * removed future tense from reference docs * removed future tense from using docs * Copy edits docs content
* removed future tense from docs content * removed future tense from developing docs * removed future tense from integrating docs * removed future tense from introduction docs * removed future tense from managing docs * removed future tense from metadata reference docs * removed future tense from quick start docs * removed future tense from reference docs * removed future tense from using docs * Copy edits docs content
* removed future tense from docs content * removed future tense from developing docs * removed future tense from integrating docs * removed future tense from introduction docs * removed future tense from managing docs * removed future tense from metadata reference docs * removed future tense from quick start docs * removed future tense from reference docs * removed future tense from using docs * Copy edits docs content
* removed future tense from docs content * removed future tense from developing docs * removed future tense from integrating docs * removed future tense from introduction docs * removed future tense from managing docs * removed future tense from metadata reference docs * removed future tense from quick start docs * removed future tense from reference docs * removed future tense from using docs * Copy edits docs content
* removed future tense from docs content * removed future tense from developing docs * removed future tense from integrating docs * removed future tense from introduction docs * removed future tense from managing docs * removed future tense from metadata reference docs * removed future tense from quick start docs * removed future tense from reference docs * removed future tense from using docs * Copy edits docs content
This reverts commit effa3c7.
This reverts commit effa3c7.
What does this PR do?
edits to documentation to standardize present tense usage over future tense.
This aligns with the Google Developer Documentation Style Guide guidance: https://developers.google.com/style/tense?hl=en
Who is reviewing it?
@shaundmorris
@jaymcnallie
@rececoffin
@sgalla
@ahoffer
Select relevant component teams:
@codice/docs
How should this be tested?
review content.
Checklist:
Notes on Review Process
Please see Notes on Review Process for further guidance on requirements for merging and abbreviated reviews.
Review Comment Legend: