From 12bff6ed7c9e00b0772923d043e5828101990f5a Mon Sep 17 00:00:00 2001 From: Valmik Date: Wed, 20 Apr 2016 13:55:48 +0530 Subject: [PATCH] Fixed spelling --- .github/CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index 1901abe906..f95b67a660 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -47,7 +47,7 @@ If you rebased your commits, you will have to [force push](http://vignette2.wiki ###Good practices: * You should rebase your branch with the branch you plan to make a Pull Request to as often as you can. -* Your commit messages should be Pull Requestecise and explain exactly what the commit does. Same goes for the Pull Request title. +* Your commit messages should be precise and explain exactly what the commit does. Same goes for the Pull Request title. * When making a PR make sure that all your code is committed properly by checking the diffs. * If you're working on different things at the same time, make sure you make separate branches for each. * Don't create new DocTypes unless absolutely necessary. If you find that there is a another DocType with a similar functionality, then please try and extend that functionality. @@ -58,4 +58,4 @@ If you rebased your commits, you will have to [force push](http://vignette2.wiki ###Glossary * remote - A remote is a connection to a Github repo. You should have two remotes, one that points to your repo and one to ours. -* rebase - When you rebase a branch, you pull commits from your remote branch and move your commits on top of it. This allows you to update your branch with the latest changes without losing your changes. \ No newline at end of file +* rebase - When you rebase a branch, you pull commits from your remote branch and move your commits on top of it. This allows you to update your branch with the latest changes without losing your changes.