4-CAIVS-user-guide/4.2-User-interfaces.md

@@ -61,8 +61,8 @@ uniform grid.
 
 -   `01` (`_CC.data_dir`)
 
-    -   `_CC.data_dir`: directory of input data (NIRVANA snapshot
-        files).
+    -   `_CC.data_dir`: directory of input data (where NIRVANA snapshot
+        files reside).
 
 -   `02` (`_CC.datafile_number`, `_CC.datafile_sequence`)
 
@@ -72,7 +72,7 @@ uniform grid.
         `NIR#.#` where the pre-dot-`#` equals `_C.mod`, i.e., the base
         filename of a snapshot is given by `NIR#` (cf. [NIRVANA:
         Snapshot
-        files](3-NIRVANA-user-guide/3.3-Output-data#snapshot-files))
+        files](https://gitlab.aip.de/ziegler/NIRVANA/-/wikis/3-NIRVANA-user-guide/3.3-Output-data#snapshot-files))
 
         *Note: CAIVS automatically recognises the number of data
         containers of a snapshot. The user just has to take care that
@@ -386,7 +386,7 @@ following table
 
 where `_C.species`, `_C.tracer` and `_C.testfields` are NIRVANA
 parameters (cf. [NIRVANA: Specification of main
-parameters](3-NIRVANA-user-guide/3.2-User-interfaces#specification-of-main-parameters))
+parameters](https://gitlab.aip.de/ziegler/NIRVANA/-/wikis/3-NIRVANA-user-guide/3.2-User-interfaces#specification-of-main-parameters))
 storing the number of species, number of tracers and number of
 testfields, respectively.
 
@@ -394,7 +394,7 @@ testfields, respectively.
 components are represented at cell-face-centroid coordinates whereas all
 other variables listed in the table are given at cell-centroid positions
 (cf. [NIRVANA: Mesh data
-structure](3-NIRVANA-user-guide/3.1-Code-basics#mesh-data-structure))*
+structure](https://gitlab.aip.de/ziegler/NIRVANA/-/wikis/3-NIRVANA-user-guide/3.1-Code-basics#mesh-data-structure))*
 
 The imported variables can be used to derive user variables as in the
 `case 1:` example above. CAIVS assumes that user variables are