From 30d08772ec6902588b43e68bb66a236eaa1ef719 Mon Sep 17 00:00:00 2001 From: Gopa Vasanth Date: Fri, 7 Dec 2018 13:20:45 +0530 Subject: [PATCH] Updated CONTRIBUTING.rst Fixed few Typos --- CONTRIBUTING.rst | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst index 717896b..5152cbc 100644 --- a/CONTRIBUTING.rst +++ b/CONTRIBUTING.rst @@ -2,13 +2,13 @@ .. image:: https://static1.squarespace.com/static/5717ef5fcf80a1deea8c70fe/5ba7976ee2c4832fe2a684d6/5ba7976ee2c4832fe2a684e5/1518919114620/Getting+Started-logo-black%285%29.png?format=750w :target: https://github.com/monsij/StudentPortal -**Open source is a shared perpective. Everyone is welcomed to contribute but without rules things get really messy. Hence it is very essential that you read through these and try to follow them as you move along.** +**Open source is a shared perspective. Everyone is welcomed to contribute but without rules, things get really messy. Hence it is very essential that you read through these and try to follow them as you move along.** ***** Step 1. Getting an issue assigned ***** * You can start either by opening a new issue or getting yourself assigned an existing one (which is currently not assigned to anyone else). -* In either case you need to understand what you want to do and how you want to implement it +* In either case, you need to understand what you want to do and how you want to implement it * In case you opening a new issue, do not forget to follow the `new-issue-guideline `_ before opening one. * To check issue assignments visit `here `_ . If you found out an unassigned issue comment under the appropriate issue and **mention the maintainers**. One of the maintainers will assign it and will label the issue. Kindly bear with this as there were some unavoidable circumstances leading to this. But surely, this won't hamper the overall process. @@ -16,19 +16,19 @@ Step 1. Getting an issue assigned Step 2. Opening a Pull Request ***** * Before you open your PR, make sure your PR contains all the applicable points as of `this template `_ . -* Additionally, mention the issue number in the PR comment as **Issue: #7** . +* Additionally, mention the issue number in the PR comment as **Issue: #7**. * After you have done so, wait for a maintainer to review and get it merged. ***** Review Process ***** -* If everything is seems great,one of the maintainers will acknowledge the commit by:: +* If everything seems great, one of the maintainers will acknowledge the commit by:: ack commit-SHA * Else you'll be seeing something like this:: unack commit-SHA - You might need to change something as per the exact requirement. + You might need to change something as per the exact requirement. ***** Here is our friendly mate...GitMate.io @@ -38,9 +38,9 @@ Here is our friendly mate...GitMate.io :target: https://gitmate.io/home -How will you help,GitMate?? +How will you help, GitMate?? ######## -"I will add labels,mark issues,run checks and everything for which I'm coded for 🥇 " +"I will add labels, mark issues, run checks and everything for which I'm coded for 🥇 " ***** Deployment:Heroku