diff options
| author | Eugen Wissner <belka@caraus.de> | 2017-07-19 07:58:20 +0200 |
|---|---|---|
| committer | Eugen Wissner <belka@caraus.de> | 2017-07-19 07:58:20 +0200 |
| commit | a0a28c76f75f16b0adbc7caae167fe87e3ed99e8 (patch) | |
| tree | 9377ef441a7d8391e65fe8325bb1b0dd2cf4d898 /CONTRIBUTING.md | |
| parent | a1f4d2bc1c095242eea212a1fca98345b3a3021f (diff) | |
| download | tanya-a0a28c76f75f16b0adbc7caae167fe87e3ed99e8.tar.gz | |
Fix CONTRIBUTING.md typos
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a98cad9..4537e02 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -60,13 +60,13 @@ After that if you visit your fork on GitHub, GitHub will suggest to create pull described on GitHub to finish the process. See [Using Pull Requests](https://help.github.com/articles/about-pull-requests/) for more information. -Please ensure that you fork is even with the upstream (original) repository. If not, you have to rebase your branch +Please ensure that your fork is even with the upstream (original) repository. If not, you have to rebase your branch on upstream/master before submitting a pull request. See https://help.github.com/articles/syncing-a-fork/ for a step-by-step guide. ### Fixing a bug -Add a unittest that demonstrates the bug along with a short description: +Add an unittest that demonstrates the bug along with a short description: ```d // Issue ###: https://issues.caraus.io/issues/###. @@ -78,7 +78,7 @@ private unittest ### Adding new features * Use Ddoc to document the feature. -* Add some unittests that demonstrate how the feature is supposed to work and prevent new bugs. +* Add some unittests that prevent new bugs and demonstrate how the feature is supposed to work. ### Style guide |