From 9c340e6ca3cee24e3042ff3d5919822d190bf881 Mon Sep 17 00:00:00 2001
From: Chris Sangwin <C.J.Sangwin@ed.ac.uk>
Date: Thu, 29 Feb 2024 16:23:35 +0000
Subject: [PATCH] Update links in the docs (WIP).

---
 doc/en/AbInitio/Authoring_quick_start_1.md | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/doc/en/AbInitio/Authoring_quick_start_1.md b/doc/en/AbInitio/Authoring_quick_start_1.md
index dff41fcbd..e8c63f959 100644
--- a/doc/en/AbInitio/Authoring_quick_start_1.md
+++ b/doc/en/AbInitio/Authoring_quick_start_1.md
@@ -10,11 +10,11 @@ The authoring quick start guide shows you how to write STACK questions.  Part 1
 We assume the following:
 
 1. You have access to a course with STACK installed.
-2. You are familiar with simple \(\LaTeX\) formatting for mathematics.  Some basic examples are provided in the [CASText](/Authoring/CASText.md) documentation.
+2. You are familiar with simple \(\LaTeX\) formatting for mathematics.  Some basic examples are provided in the [CASText](../Authoring/CASText.md) documentation.
 
 ## Creating a minimal STACK question
 
-Go to your Course, navigate to the [question bank](/Moodle/Question_bank.md) and create a new question with the "STACK" question type.
+Go to your Course, navigate to the [question bank](../Moodle/Question_bank.md) and create a new question with the "STACK" question type.
 
 There are lots of fields, but only a few are compulsory:
 
@@ -23,7 +23,7 @@ There are lots of fields, but only a few are compulsory:
 3. The teacher's "model answer" (inside "Input: ans1" on a default question),
 4. A test of "correctness".
 
-By default a new question automatically has one [input](/Authoring/Inputs.md), and one algorithm to test correctness of the answer.
+By default a new question automatically has one [input](../Authoring/Inputs.md), and one algorithm to test correctness of the answer.
 
 ### Question name ###
 
@@ -47,7 +47,7 @@ Notes:
 
 ## Input: ans1
 
-Scroll down:  there will be an [inputs](/Authoring/Inputs.md) section of the editing form.  Click on the header `Input: ans1` to reveal the relevant settings.
+Scroll down:  there will be an [inputs](../Authoring/Inputs.md) section of the editing form.  Click on the header `Input: ans1` to reveal the relevant settings.
 
 For a minimal question, we must specify the _model answer_. Let this be
 
@@ -57,16 +57,16 @@ Notes
 
 1. The student's response is stored in the answer variable `ans1`.
 2. The model answer must be a syntactically valid expression in CAS (Maxima) syntax, not LaTeX. This means multiplication must be explicitly specified, using `*`.
-3. [Inputs](/Authoring/Inputs.md) can have a variety of types selected by the  _Input type_ drop-down menu.  The _Algebraic input_ is the default, and what we need here.
+3. [Inputs](../Authoring/Inputs.md) can have a variety of types selected by the  _Input type_ drop-down menu.  The _Algebraic input_ is the default, and what we need here.
 4. A question can have many inputs for multiple parts.  These are discussed later in a later part.
 
 ## Assessing correctness of a response - the Potential Response Tree (PRT)
 
 Next we have to decide if the student's answer is correct.
 
-To grade the student's response, we need to determine its mathematical properties using an algorithm known as a [potential response tree](/Authoring/Potential_response_trees.md).
+To grade the student's response, we need to determine its mathematical properties using an algorithm known as a [potential response tree](../Authoring/Potential_response_trees.md).
 
-By default, a new question contains one [potential response tree](/Authoring/Potential_response_trees.md) called `prt1`.  Feedback generated by the tree replaces the tag `[[feedback:prt1]]` at the appropriate time.
+By default, a new question contains one [potential response tree](../Authoring/Potential_response_trees.md) called `prt1`.  Feedback generated by the tree replaces the tag `[[feedback:prt1]]` at the appropriate time.
 
 ### Configuring a potential response node
 
@@ -79,8 +79,8 @@ A potential response tree is a non-empty acyclic directed graph of _potential re
 Each branch can then
 
 * Assign/update the score,
-* Assign formative [feedback](/Authoring/Feedback.md) to the student,
-* Leave an [answer note](/Authoring/Potential_response_trees.md#Answer_note) for statistical [reporting](/Authoring/Reporting.md) purposes,
+* Assign formative [feedback](../Authoring/Feedback.md) to the student,
+* Leave an [answer note](../Authoring/Potential_response_trees.md#Answer_note) for statistical [reporting](../Authoring/Reporting.md) purposes,
 * Continue to the next potential response node, or end the process with `[stop]`.
 
 Let us configure the first node to determine if the student has differentiated correctly.
@@ -128,7 +128,7 @@ First is "validation", and normally servers have "instant validation" enabled.
 
 The second stage executes when a valid expression is entered, and this evaluates the potential response tree to assess the student's answer.
 
-This two-stage process is a unique and essential feature of STACK.  There are lots of options for validation to help the student.  For example, in the above, all example expressions have strict syntax.  Here we used expressions like `3*(x-1)^2`, with `*` symbols to denote multiplication.  You could choose to let students type in expressions like `3(x-1)^2` and accept implied multiplication. Note, however, that teacher input will always have to be strict to avoid ambiguity. Documentation on these options is given in the [inputs](/Authoring/Inputs.md) section.
+This two-stage process is a unique and essential feature of STACK.  There are lots of options for validation to help the student.  For example, in the above, all example expressions have strict syntax.  Here we used expressions like `3*(x-1)^2`, with `*` symbols to denote multiplication.  You could choose to let students type in expressions like `3(x-1)^2` and accept implied multiplication. Note, however, that teacher input will always have to be strict to avoid ambiguity. Documentation on these options is given in the [inputs](../Authoring/Inputs.md) section.
 
 # Next step #
 
-- 
GitLab