diff options
| author | flack <flack@contentcontrol-berlin.de> | 2017-03-23 14:48:14 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-03-23 14:48:14 +0100 |
| commit | cc995e26c2dd112ace00e1e76cd58a365f6928a3 (patch) | |
| tree | f683c44740957b5e7aaa4041f3fd1fa4c921b060 | |
| parent | a230b0588788dbe1ac84622aea169c577b381241 (diff) | |
add missing spaces so that markdown recognizes headline
| -rw-r--r-- | CONTRIBUTING.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index fc8d58d97d..0766d89f55 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -130,7 +130,7 @@ pull requests which attempt to do too much, are overly large, or overly complex as this makes review difficult. -###Features +### Features When adding a new feature, thought must be given to the long term technical debt and maintenance that feature may require after inclusion. Before proposing a new @@ -139,7 +139,7 @@ maintain it (including bug fixing). If features get orphaned with no maintainer in the future, they may be removed by the Repository Maintainer. -###Refactoring +### Refactoring Refactoring is a necessary part of any software project's evolution. The following guidelines cover refactoring pull requests for the project. @@ -187,7 +187,7 @@ other kinds of patches because of increased peer review and consensus building requirements. -###Peer Review +### Peer Review Anyone may participate in peer review which is expressed by comments in the pull request. Typically reviewers will review the code for obvious errors, as well as |