From dc6979862e6e74f0acdd08f9cdd32a56992531b0 Mon Sep 17 00:00:00 2001 From: Marcus Date: Wed, 4 Jan 2017 22:29:45 -0600 Subject: [PATCH] typo fix --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 9d49a3795..099e6ca07 100644 --- a/README.md +++ b/README.md @@ -296,8 +296,8 @@ Pulling seperate PR's to test code is cumbersome and we realize that. To help wi When You do perform a pull request, you should set the title of it so that others know no one has looked at it yet. - If you just submitted the PR, your title should look like this: `[language]challenge_[chalNumber](UnReviewed)` -- If you have already recieved one review, your PR title should look like this: `[language]challenge_[#](Pending)` -- If you have at least 2 reviews, set your pull request to this: `[language]challenge_[#](ReadyForMerge)` and a mod will merge your code to the main repository. +- If you have already recieved one review, your PR title should look like this: `[language]challenge_[chalNumber](Pending)` +- If you have at least 2 reviews, set your pull request to this: `[language]challenge_[chalNumber](ReadyForMerge)` and a mod will merge your code to the main repository. Taking this approach to code review will help to streamline the process and make reviews easier for everyone involved. Take the time to check your github notifications so that you can check to see if anyone has reviewed your code yet.