From be80c501d7c0d30ecd2b64262213f1fb9ac7c80e Mon Sep 17 00:00:00 2001
From: Chris Hill-Scott <me@quis.cc>
Date: Mon, 20 Jun 2016 15:59:39 +0100
Subject: [PATCH] Use less confusing terminology than yes/no
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Yes/no is quite ambiguous. Correct/incorrect is more formal, but
clearer.

Right/wrong doesn’t feel quite right. Good/bad is definitely not right.
---
 .../partials/templates/guidance-personalisation.html          | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/app/templates/partials/templates/guidance-personalisation.html b/app/templates/partials/templates/guidance-personalisation.html
index c395f42e6..3cae73723 100644
--- a/app/templates/partials/templates/guidance-personalisation.html
+++ b/app/templates/partials/templates/guidance-personalisation.html
@@ -5,10 +5,10 @@
       Use double brackets to add personalisation.
     </p>
     <p>
-      Yes: ((name))
+      Correct: ((name))
     </p>
     <p>
-      No: ((Helen))
+      Incorrect: ((Helen))
     </p>
   </div>
 </details>