From 2788e8696087f71dec46c720b40f5abe52ba7589 Mon Sep 17 00:00:00 2001
From: Dale Wijnand <344610+dwijnand@users.noreply.github.com>
Date: Mon, 14 May 2018 18:01:45 +0200
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 d682264..f9e872e 100644
--- a/Good-First-Issues.md
+++ b/Good-First-Issues.md
@@ -25,7 +25,7 @@ Steps:
 1. **Links**: Link to the relevant code, PRs, issue threads, docs, etc
 2. **Solution**: Add comments/hints on how to resolve the issue (and non-solutions)
 3. **Testing**: Try and give testing tips, ideally link to prior art
-4. **Motivation** (optional): Explain the change's relevance or purpose (to motivate the contribution)
+4. **Motivation** (optional): Explain the change's relevance or purpose
 5. **Background** (optional): Explain the code's behaviour, structure, or context
 
 It's common that it takes longer to write mentoring instructions than to fix it yourself (as an experienced