maverick/docbrown
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Improved grammar in README.md (#663)

Browse source
This commit is contained in:
Alexander Minderov 2018-09-20 09:03:05 -07:00 • committed by Ben Halpern
parent 2545b8d77f
commit 11b81daedc
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
README.md
View file

@ -89,7 +89,7 @@ When in doubt, ask a [core team member](#core-team)! You can mention us in any i
### Create an issue
Nobody's perfect. Something doesn't work? or could be done better? Let us know by creating an issue.
Nobody's perfect. Something doesn't work? Or could be done better? Let us know by creating an issue.
PS: a clear and detailed issue gets lots of love, all you have to do is follow the issue template!
@ -99,9 +99,9 @@ Some existing code may be poorly written or untested, so we must have more scrut
#### Create a pull request
* Try to keep the pull requests small; a pull request should try its very best to address only a single concern.
* Try to keep the pull requests small. A pull request should try its very best to address only a single concern.
* Make sure all tests pass and add additional tests for the code you submit. [More info here](https://docs.dev.to/testing/)
* Document your reasoning behind the changes. Explain why you wrote the code in the way you did; the code should explain what it does.
* Document your reasoning behind the changes. Explain why you wrote the code in the way you did. The code should explain what it does.
* If there's an existing issue related to the pull request, reference to it by adding something like `References/Closes/Fixes/Resolves #305`, where 305 is the issue number. [More info here](https://github.com/blog/1506-closing-issues-via-pull-requests)
* If you follow the pull request template, you can't go wrong.