fix broken links

Signed-off-by: Rieks <[email protected]>
tno-terminology-design · Apr 16, 2024 · 2081430 · 2081430
1 parent 5bbd48e
commit 2081430
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs/how-to/generate-hrgs.md b/docs/how-to/generate-hrgs.md
@@ -5,11 +5,11 @@ title: Generate Glossaries
 # How To Generate (Human Readable) Glossaries
 
 The generation of [human readable glossaries](@tev2) consists of
-finding [MRGRef](tev2) markers in a file, and
+finding [MRGRef](@tev2) markers in a file, and
 replacing them with a chunk of characters that,
 when rendered, typically list the definitions of the [terms](@tev2)
 as specified in the one particular [machine readable glossary](@tev2)
-that is specified in the [MRGRef](tev2).
+that is specified in the [MRGRef](@tev2).
 
 What a particular [entry in the glossary](hrg-entry@tev2) would actually look
 like can be customized by creating and using so-called [converters](@tev2).

diff --git a/docs/how-to/generate-mrgs.md b/docs/how-to/generate-mrgs.md
@@ -5,7 +5,7 @@ title: Generate MRGs
 # How To Generate (Machine Readable) Glossaries
 
 The generation of [machine readable glossaries (MRGs)](mrg@tev2) consists of
-finding the specifications of the [terminologies](tev2) for which such 
+finding the specifications of the [terminologies](@tev2) for which such 
 [MRGs](@tev2) are to be created, and then generate them.
 
 This results in the generated [MRGs](@tev2) to become available in the