Various corrections (typos etc.) and minor additions.

Author: klust

docs/2022-CSC_and_LO/1_Intro/1_01_what_is_easybuild.md

@@ -95,7 +95,7 @@ By default EasyBuild tries to run tests if the build process of a package provid
 functionality, or can run simple tests of its own, and of course these tests will fail if 
 the host CPU does not support the full instruction set of the target CPU. Secondly, more
 and more software has broken build processes where developers thought that it was a good 
-idea to hard-code options such as ``-march=native`` or ``--xHost`` in a way that EasyBuild
+idea to hard-code options such as ``-march=native`` or ``-xHost`` in a way that EasyBuild
 cannot easily overwrite those.
 
 

docs/2022-CSC_and_LO/1_Intro/1_03_CPE.md

@@ -13,7 +13,7 @@ tools and to configure the environment in a flexible way.
 
 ---
 
-## Cray PE components
+## HPE Cray PE components
 
 ### Cray compiler environments
 
@@ -185,9 +185,7 @@ versions of the library are supported, the finalised LUMI system will only suppo
 ### DSMML
 
 * Modules: `cray-dsmml`
-* 
 * Manpages: `intro_dsmml`
-* 
 * Website: [https://pe-cray.github.io/cray-dsmml](https://pe-cray.github.io/cray-dsmml)
 
 Distributed Symmetric Memory Management Library (DSMML) is a HPE Cray proprietary memory management library.

docs/2022-CSC_and_LO/1_Intro/1_04_LUMI_software_stack.md

@@ -98,7 +98,7 @@ set of target modules after loading the ``CrayEnv`` module.
 
 ## The ``partition`` module
 
-The ``LUMI`` module currently supports four partition modules, but that number may
+The ``LUMI`` module currently supports five partition modules, but that number may
 be reduced in the future:
 
 | Partition         | CPU target            | Accelerator                 |

docs/2022-CSC_and_LO/1_Intro/1_08_basic_usage.md

@@ -143,18 +143,18 @@ while `eb -S` produces a more concise output.
 For example, let's check which easyconfig files are available for OpenFOAM 8 with a `foss` toolchain:
 
 ```shell
-$ eb --search openfoam-8-foss
- * /home/example/.local/easybuild/easyconfigs/o/OpenFOAM/OpenFOAM-8-foss-2020a.eb
- * /home/example/.local/easybuild/easyconfigs/o/OpenFOAM/OpenFOAM-8-foss-2020b.eb
+$ eb --search openfoam-9
+ * /appl/lumi/LUMI-EasyBuild-contrib/easybuild/easyconfigs/o/OpenFOAM/OpenFOAM-9-cpeGNU-21.08.eb
+ * /appl/lumi/LUMI-EasyBuild-contrib/easybuild/easyconfigs/o/OpenFOAM/OpenFOAM-9-cpeGNU-21.12.eb
 ```
 
 The output is a bit more condensed when using `eb -S`:
 
 ```shell
-$ eb -S openfoam-8-foss
-CFGS1=/home/example/.local/easybuild/easyconfigs/o/OpenFOAM
- * $CFGS1/OpenFOAM-8-foss-2020a.eb
- * $CFGS1/OpenFOAM-8-foss-2020b.eb
+$ eb -S openfoam-9
+CFGS1=/appl/lumi/LUMI-EasyBuild-contrib/easybuild/easyconfigs/o/OpenFOAM
+ * $CFGS1/OpenFOAM-9-cpeGNU-21.08.eb
+ * $CFGS1/OpenFOAM-9-cpeGNU-21.12.eb
 ```
 
 Note that the search is performed *case-insensitive*.
@@ -164,13 +164,17 @@ or other special characters like `^` or `$` to mark the start/end of the filenam
 but you need to be careful that `bash` does not expand these before the `eb` command is started,
 so it is recommended to wrap the search pattern in single quotes (`'...'`) when using wildcards.
 
-For example, to check which easyconfigs are available to install TensorFlow 2.4.1 with the `2020b` version of a toolchain:
+For example, to check which easyconfigs are available to install GROMACS 2021 and subversions with 
+the `cpeGNU` toolchains:
 
 ```shell
-$ eb -S '^tensorflow-2.4.1.*2020b'
-CFGS1=/home/example/.local/easybuild/easyconfigs/t/TensorFlow
- * $CFGS1/TensorFlow-2.4.1-foss-2020b.eb
- * $CFGS1/TensorFlow-2.4.1-fosscuda-2020b.eb
+$ eb -S '^gromacs-2021.*cpeGNU.*'
+CFGS1=/appl/lumi/LUMI-EasyBuild-contrib/easybuild/easyconfigs/g/GROMACS
+ * $CFGS1/GROMACS-2021-cpeGNU-21.08-PLUMED-2.7.2-CPU.eb
+ * $CFGS1/GROMACS-2021.3-cpeGNU-21.08-CPU.eb
+ * $CFGS1/GROMACS-2021.4-cpeGNU-21.12-PLUMED-2.7.4-CPU.eb
+ * $CFGS1/GROMACS-2021.4-cpeGNU-21.12-PLUMED-2.8.0-CPU.eb
+ * $CFGS1/GROMACS-2021.5-cpeGNU-21.12-CPU.eb
 ```
 
 ---

docs/2022-CSC_and_LO/2_Using/2_02_creating_easyconfig_files.md

@@ -44,16 +44,24 @@ specific for a certain compiler and don't recognise the Cray compilers.
 Reasons to consider implementing a software-specific easyblock rather than using a generic easyblock include:
 
 -   'critical' values for easyconfig parameters required to make installation succeed;
--   toolchain-specific aspects of the build and installation procedure (e.g., configure options);
--   interactive commands that need to be run;
-    *For example: The easyblock to [install maple](https://github.com/easybuilders/easybuild-easyblocks/blob/develop/easybuild/easyblocks/m/maple.py) 
-    responds to a number of interactive questions.* 
--   custom (configure) options for dependencies;
+    *For example, the [easyblock for bowtie2](https://github.com/easybuilders/easybuild-easyblocks/blob/develop/easybuild/easyblocks/b/bowtie2.py)
+    defines a number of variables used in the Makefile are specified on the make command line to ensure that the right
+    compilers are used.*
+-   toolchain-specific aspects of the build and installation procedure (e.g., configure options);  
+    *For example, the [easyblock for CP2K](https://github.com/easybuilders/easybuild-easyblocks/blob/develop/easybuild/easyblocks/c/cp2k.py) 
+    will add several compiler options when compiling with gcc and gfortran, including the infamous
+    `-fallow-argument-mismatch` which is required from gfortran 10 on for many older codes.*
+-   custom (configure) options for dependencies;  
     *For example, the [easyblock for VMD](https://github.com/easybuilders/easybuild-easyblocks/blob/develop/easybuild/easyblocks/v/vmd.py)
     will add configure options depending on the dependency list of the package.*
--   having to create or adjust specific (configuration) files;
+-   interactive commands that need to be run;  
+    *For example: The [easyblock for maple](https://github.com/easybuilders/easybuild-easyblocks/blob/develop/easybuild/easyblocks/m/maple.py) 
+    responds to a number of interactive questions.* 
+-   having to create or adjust specific (configuration) files;  
+    *For example, the [easyblock for Siesta](https://github.com/easybuilders/easybuild-easyblocks/blob/develop/easybuild/easyblocks/s/siesta.py)
+    edits one of the configuration files through regular expressions.*
 -   'hackish' usage of a generic easyblock;
--   complex or very non-standard installation procedure;
+-   complex or very non-standard installation procedure;  
     *For example, the [easyblock to install the gcc compilers from source](https://github.com/easybuilders/easybuild-easyblocks/blob/develop/easybuild/easyblocks/g/gcc.py),
     bootstrapping with the system compiler and then re-installing with itself.* 
 
@@ -499,13 +507,30 @@ Or, to try using a different compiler toolchain you can use `--try-toolchain`:
 eb example-1.2.3-foss-2020b.eb --try-toolchain cpeCray,21.12
 ```
 
+There is also a `--try`  option to change an arbitrary parameter in an easyconfig:
+
+```shell
+eb example-1.2.3-foss-2020b.eb --try-amend versionsuffix='-test'
+```
+
+Its general syntax is 
+
+```
+--try-amend=VAR=VALUE[,VALUE]
+```
+
+This option can be used multiple times also to make multiple changes.
+
 It is important to keep in mind the *"try"* aspect here: while easyconfigs that
 are generated by EasyBuild via a `--try-*` option often do work fine, there is
 no strong guarantee they will. Newer software versions may come with changes to
 the installation procedure, additional dependencies that are required, etc.
 Using a different compiler toolchain may be as simple as just switching one for
 another, but it may require additional changes to be made to configure options, for example.
 
+The easyconfig files modified in this way will be stored in the `easybuild` subdirectory 
+of the software installation directory and in the easyconfig archive that EasyBuild creates.
+
 ## Copying easyconfigs
 
 One additional handy command line option we want to highlight is `--copy-ec`, which can be used to