From 16d1440590c1927001def111b3f8db84519a37ec Mon Sep 17 00:00:00 2001
From: Pat <52056183+NeuroShepherd@users.noreply.github.com>
Date: Tue, 3 Sep 2024 09:33:48 +0000
Subject: [PATCH] Fix error in documentation.qmd

---
 documentation.qmd | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation.qmd b/documentation.qmd
index e00418f..c580549 100644
--- a/documentation.qmd
+++ b/documentation.qmd
@@ -174,7 +174,7 @@ Machine-readability refers to the ability of machines (computers, algorithms, et
 
 We already established that metadata and README files are strongly connected. They form a great way to provide an introduction to and documentation of a dataset and its research context. A README file is a plain text file often written in markdown and then named "README.md". This naming convention helps spotting the README file for humans and machines alike, e.g. in GitHub repositories the README.md file is identified automatically and its content displayed on the repositories main page. The README file should be one of the first files your create for a new project. You can then continue filling it with the relevant information.
 
-What should be in a README file? - Ideally all the answers to the questions posed under the metadata section should be given in the README file. To determine what should be best included in your README file, it can also be helpful to go through the questions of a [Research Data Management Plan](RDMP.qmd). While your README file should be very descriptive, it is also important to stay concise and clear. Avoid e.g. using jargon to improve inter-disciplinary usage.
+What should be in a README file? - Ideally all the answers to the questions posed under the metadata section should be given in the README file. To determine what should be best included in your README file, it can also be helpful to go through the questions of a [Research Data Management Plan](dmp.qmd). While your README file should be very descriptive, it is also important to stay concise and clear. Avoid e.g. using jargon to improve inter-disciplinary usage.
 
 ::: {.callout-tip}
 # Task 2.2: (~10 min)