From 82b83fe1b8952c53111c49c2bf0db1f91518e063 Mon Sep 17 00:00:00 2001 From: Angelos Chalaris Date: Thu, 21 Dec 2017 11:48:36 +0200 Subject: [PATCH] Fix markup --- COLLABORATING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/COLLABORATING.md b/COLLABORATING.md index 3629eba70..e5f17c034 100644 --- a/COLLABORATING.md +++ b/COLLABORATING.md @@ -9,7 +9,7 @@ As a member of the team that manages **30 seconds of code**, you have the follow - **Be part of the conversation in the issue tracker.** That includes (but is not limited to) helping out new members, discussing new features and explaining decisions to people. - **Review pull requests.** You do not have to read through all of the pull requests and review them, but taking the time each day to review a few can help a great deal. - **Be civil and polite.** If you are about to lose your temper, take a step back and go do something else. We want our interactions with the community to be polite, so that more people can join the project and contribute in any way they can. Remember to always thank contributors for their help, even if its minor changes or changes that did not make it into the project. This way we can reward and encourage people to keep being part of the community. -- Contribute when you want, moderate when you can. If you have a lot on your plate outside of this project, it's alright. It's better to take a break for a few days rather than hastily deal with issues and pull requests that might break things. +- **Contribute when you want, moderate when you can.** If you have a lot on your plate outside of this project, it's alright. It's better to take a break for a few days rather than hastily deal with issues and pull requests that might break things. ## Guidelines for merging pull requests and making changes to the project