From 2620e08d2db722e4fce55c5402993b4ee8830a25 Mon Sep 17 00:00:00 2001
From: Dale Wijnand <344610+dwijnand@users.noreply.github.com>
Date: Wed, 11 Apr 2018 16:05:37 +0100
Subject: [PATCH] Updated Good First Issues (markdown)

---
 Good-First-Issues.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Good-First-Issues.md b/Good-First-Issues.md
index 69ffa89..e7602ab 100644
--- a/Good-First-Issues.md
+++ b/Good-First-Issues.md
@@ -33,7 +33,7 @@ To convert an issue (e.g a [help wanted][] issue) so that it's ready for a new c
 8. add links to pre-existing tests and give tips on how to test the change (if possible)
 9. detail who the contributor can ask for help, and by which means ([sbt/sbt-contrib][], issue comments, etc)
 10. make sure that any additional steps to take are explained or mentoring advice is given
-11. finally, review the issue and see if you can make it more friendly and/or consise
+11. finally, review the issue and see if you can make it more friendly and/or concise
 
 In effect it should actually take longer to write the the issue than to fix it yourself (as an experienced
 maintainer), but that extra time is an investment in [making sbt easier to contribute to][].