From 3023f087022e15b81689d4faa22f880547c6df81 Mon Sep 17 00:00:00 2001 From: Rahul-3000 <52457974+Rahul-3000@users.noreply.github.com> Date: Wed, 19 Aug 2020 01:57:47 +0530 Subject: [PATCH] Grammatical mistakes edited in CONTRIBUTING.md (#673) --- CONTRIBUTING.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3bab9c1..24163d3 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -3,7 +3,7 @@ Please ensure your pull request adheres to the following guidelines: - Search previous suggestions before making a new one, as yours may be a duplicate. -- Make sure your contribution is useful and relevant before submitting. That implies it having enough content and every item has a good succinct description. +- Make sure your contribution is useful and relevant before submitting. That implies it has enough content and every item has a good succinct description. - Make an individual pull request for each suggestion. - Use the following format: `- [Repository Name](link-to-repository-label) _(label: beginner-friendly-label-in-the-repository)_
Description` - Example link formatting: `- [awesome-for-beginners](https://github.com/MunGell/awesome-for-beginners/labels/good-first-contribution) _(label: good-first-contribution)_
A list of awesome beginners-friendly projects.` @@ -12,12 +12,12 @@ Please ensure your pull request adheres to the following guidelines: - Check your spelling and grammar. - Make sure your text editor is set to remove trailing whitespace. - The pull request and commit should be given a meaningful title. -- Make sure to give a description about your pull request. -- If the label does not clearly state its "beginner friendly" purpose, please make sure to confirm with the maintainer that it is used for such issues. Please include the link to where maintainer confirms it in the PR. See examples below: +- Make sure to describe your pull request. +- If the label does not clearly state its "beginner friendly" purpose, please make sure to confirm with the maintainer that it is used for such issues. Please include the link to where maintainer approves it in the PR. See examples below: - Repository called "HornsAndHoovesJs" has label `good-first-contribution`. This PR does not need to be confirmed with the maintainer and can be merged straight away. - Repository called "bicycle-wheels-php" has label `easy`. This PR must be confirmed with the maintainer of "bicycle-wheels-php". The issue link where the maintainer confirms that label `easy` is used in the repository for beginner-friendly tasks has to be provided in the PR description. - Maintainer confirmation is also required in case repository has more than one beginner-friendly-like label (e.g. `low-hanging-fruit` and `up-for-grabs`). -- Contributed repository must be maintained, have an active community to be able to help newcomers and have issues with an appropriate label. +- The contributed repository must be maintained, have an active community to be able to help newcomers and have issues with an appropriate label. - Links must be pointing directly to the repository, no tracking links allowed. This list is not for advertising purposes. Thank you for your suggestions!