Correcting a number of links.

Author: klust

docs/2022-CSC_and_LO/1_06_installation.md

@@ -424,7 +424,7 @@ We do so only for the framework and easyblocks files as the easconfig files are
 install EasyBuild. Instead we create our own EasyConfig file for EasyBuild which contains
 some additional packages that enable extra features in EasyBuild and also provide more information
 to Lmod. Next the configuration module for EasyBuild (see the next section, 
-["Configuring EasyBuild"](1_06_configuring.md), for more information) and use the temporary 
+["Configuring EasyBuild"](1_07_configuration), for more information) and use the temporary 
 installation of EasyBuild with our own EasyConfig file to do a proper installation of EasyBuild
 with module in the final location.
 
@@ -468,7 +468,7 @@ eb --show-config
 ```
 
 This should tell you that EasyBuild (ab)uses `$HOME/.local/easybuild` as a default location.
-More on configuring EasyBuild in the [next part of the tutorial](configuration.md).
+More on configuring EasyBuild in the [next part of the tutorial](configuration).
 
 #### System information
 

docs/2022-CSC_and_LO/1_07_configuration.md

@@ -280,7 +280,7 @@ The default `EasyBuildMNS` module naming scheme roughly corresponds to the filen
 and consists of the software name followed by a combination of the software version, toolchain and
 an optional label (which corresponds to the value of the `versionsuffix` easyconfig parameter):
 `<name>/<version><-toolchain><versionsuffix>`. Just like with [names of easyconfig
-files](terminology.md#easyconfig-files), the `<-toolchain>` part is omitted when the `system` toolchain is used,
+files](1_05_terminology#easyconfig-files), the `<-toolchain>` part is omitted when the `system` toolchain is used,
 and the `<versionsuffix>` value is empty by default.
 
 !!! Note "Module naming scheme on LUMI"
@@ -366,9 +366,9 @@ across different software installations. They define *configuration settings*,
 such as the location where software should be installed, or the syntax that should
 be used when generating module files.
 
-An [easyconfig file](terminology.md#easyconfig-files) (`*.eb`) on the other hand *specifies the details for one particular software installation*.
+An [easyconfig file](1_05_terminology#easyconfig-files) (`*.eb`) on the other hand *specifies the details for one particular software installation*.
 It does this by defining a set of *easyconfig parameters*, which tell EasyBuild the name and version
-of the software to install, which [toolchain](terminology.md#toolchains) and [easyblock](terminology.md#easyblocks) to use, etc.
+of the software to install, which [toolchain](1_05_terminology#toolchains) and [easyblock](1_05_terminology#easyblocks) to use, etc.
 
 For each software installation performed by EasyBuild, there is a corresponding easyconfig file.
 There typically are only a handful of configuration files used however, for example a system-level

docs/2022-CSC_and_LO/2_02_creating_easyconfig_files.md

@@ -1,6 +1,6 @@
 # Creating easyconfig files
 
-*[[back: Troubleshooting]](2_02_troubleshooting.md)*
+*[[back: Troubleshooting]](2_02_troubleshooting)*
 
 ---
 
@@ -58,7 +58,7 @@ Reasons to consider implementing a software-specific easyblock rather than using
     bootstrapping with the system compiler and then re-installing with itself.* 
 
 For implementing easyblocks we refer to the 
-["Implementing easyblocks" section of this tutorial](2_03_implementing_easyblocks.md)
+["Implementing easyblocks" section of this tutorial](2_03_implementing_easyblocks)
 and the [EasyBuild documentation](https://docs.easybuild.io/en/latest/Implementing-easyblocks.html).
 
 ## Writing easyconfig files
@@ -1024,4 +1024,4 @@ You can leverage the `eb-tutorial` easyconfig file we have composed in the examp
 
 ---
 
-*[[next: Using external modules from the Cray PE]](2_03_external_modules.md)*
+*[[next: Using external modules from the Cray PE]](2_03_external_modules)*

docs/2022-CSC_and_LO/2_03_external_modules.md

@@ -1,6 +1,6 @@
 # Using external modules from the Cray PE
 
-*[[back: Creating easyconfig files]](2_02_creating_easyconfig_files.md)*
+*[[back: Creating easyconfig files]](2_02_creating_easyconfig_files)*
 
 ---
 

docs/2022-CSC_and_LO/3_03_slurm_jobs.md

@@ -37,8 +37,8 @@ will be *passed down* into the submitted job automatically, via command line opt
 command that is run in the job script.
 
 This includes not only command line options used next to ``--job``, but also configuration settings
-that are specified via an [EasyBuild configuration file](configuration.md#configuration-files) or through
-[``$EASYBUILD_*`` environment variables](configuration.md#easybuild_-environment-variables).
+that are specified via an [EasyBuild configuration file](1_07_configuration#configuration-files) or through
+[``$EASYBUILD_*`` environment variables](1_07_configuration#easybuild_-environment-variables).
 
 This implies that any EasyBuild configuration files or ``$EASYBUILD_*`` environment variables
 that are in place in the job environment are most likely *irrelevant*, since configuration settings
@@ -330,4 +330,4 @@ $ module avail AUGUSTUS
 
 ---
 
-*[[next: Module naming schemes]](3_04_module_naming_scheme.md)*
+*[[next: Module naming schemes]](3_04_module_naming_scheme)*