docs: fix typos and grammar in guidelines - #644
Open
Avicennasis wants to merge 1 commit into
Open
Conversation
Signed-off-by: Léon Avic Simmons <Avicennasis@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes 10 typos / grammar errors across 3 documentation files in
docs/:docs/DEPRECATE-GUIDELINES.md
ie:->i.e.:(3 occurrences - abbreviation punctuation)There are some ongoing discussion->ongoing discussionsIf there're no responses->If there are no responsesdocs/governance.md
This may the case with projects->This may be the case with projectsexpectations around writing unit test,->writing unit tests,all further decision making. (technical or otherwise).->all further decision making (technical or otherwise).(stray sentence-ending period before the parenthetical)docs/PUBLISH-GUIDELINES.md
but it also offer two methods->but it also offers two methodsUse one base on your preference->Use one based on your preference(markdown table column padding adjusted by one space so the table stays aligned)No functional changes - documentation prose only. No identifiers, code samples, or command strings were altered.
The commit is signed off per the Developer's Certificate of Origin 1.1 in CONTRIBUTING.md.