From 86408ea9e0976063825a12addeaf819473f363e9 Mon Sep 17 00:00:00 2001
From: smmercuri <smercuri@ed.ac.uk>
Date: Tue, 14 May 2024 10:12:05 +0100
Subject: [PATCH] Tidy guide

---
 doc/en/Topics/Matching.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/en/Topics/Matching.md b/doc/en/Topics/Matching.md
index dee8e85b9..c2908c74c 100644
--- a/doc/en/Topics/Matching.md
+++ b/doc/en/Topics/Matching.md
@@ -139,7 +139,7 @@ ans: [
 Here we should:
 - Write the question text itself.
 - Open the `parsons` block with `input` and `columns` header parameters.
-- Transfer the variables from `Question variables` into a JSON inside the `parsons` block as appropriate.
+- Transfer the variables from _Question variables_ into a JSON inside the `parsons` block as appropriate.
 - Close the `parsons` block.
 - Set `style="display:none"` in the input div to hide the messy state from the student.
 
@@ -214,7 +214,7 @@ You will use the `"<ID>"` string to write solutions and assess student inputs; t
 - The headers that will appear on top of the answer columns.
 - The correct answer as a two-dimensional array. This should always be column grouped.
 
-For our example, the `Question variables` field looks as follows.
+For our example, the _Question variables_ field looks as follows.
 ```
 stack_include("contribl://matchlib.mac");
 
@@ -247,7 +247,7 @@ ans: [
 Here we should:
 - Write the question text itself.
 - Open the `parsons` block with `input`, `columns` and `rows` header parameters.
-- Transfer the variables from `Question variables` into a JSON inside the `parsons` block as appropriate.
+- Transfer the variables from _Question variables_ into a JSON inside the `parsons` block as appropriate.
 - Close the `parsons` block.
 - Set `style="display:none"` in the input div to hide the messy state from the student.
 
-- 
GitLab