https://git.reactos.org/?p=reactos.git;a=commitdiff;h=f50f983f451e3df2e9bab55853f089755164c92b
commit f50f983f451e3df2e9bab55853f089755164c92b Author: Alexander Shaposhnikov <[email protected]> AuthorDate: Thu Mar 22 10:44:01 2018 +0200 Commit: GitHub <[email protected]> CommitDate: Thu Mar 22 10:44:01 2018 +0200 [CONTRIBUTING] Fix typo --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2d4b903b40..3cbab7b9f7 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -49,7 +49,7 @@ Your contribution can be of numerous forms. We currently accept two ways to cont ### Pull Requests -Since our [migration to GitHub] we gladly accept __[Pull Requests]__. Pull requests let you tell others about changes you have pushed to a repository on GitHub. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before the changes are merged into the repository. __Pull request is a prefered way to submit your work__ - it makes reviewing and merging your contribution much easier. +Since our [migration to GitHub] we gladly accept __[Pull Requests]__. Pull requests let you tell others about changes you have pushed to a repository on GitHub. Once a pull request is opened, you can discuss and review the potential changes with collaborators and add follow-up commits before the changes are merged into the repository. __Pull request is a preferred way to submit your work__ - it makes reviewing and merging your contribution much easier. ### Patches @@ -65,7 +65,7 @@ Our commit style is defined in a __[commit template]__. Use it as a reference or - *Use your __real name__ and __real email__.* We do not accept anonymous contributions! - *Ensure your contribution is properly described.* Include the relevant issue number if applicable. -- *Put only related changes.* It will make reviewing easier as the reviewer needs to recall less information about the existing source code that is changed. +- *Put only related changes.* It will make reviewing easier as the reviewer needs to recall less information about the existing source code that is changed./rapps-db/commit/7737182148cde7c559fb21170d3e5c3acf42648c.patch - *Search for similar pull requests/patches before submitting.* It may be that a similar pull request or issue was opened previously. Comment and review on that one instead. - *Keep your contribution small and focused on the topic.* It can be tempting to fix existing issues as you come across them while reading the source code. Resist the temptation and put in a note in the source code instead, or (even better) put the issue in the issue tracking system. - *Respect our __[Coding Style]__ and __[Programming Guidelines]__.*
