Context Navigation

Information_on_software

-                      v8
+                      v9
 The software made available on the new stack via Easybuild is arranged hierarchically, with only some core modules made available to the user at login. Typically, these core modules include the compilers, or some other standalone tools (i.e. JUBE). Loading such core modules via `module load` allows the list of available modules to increase, including the modules that are installed with the fore-mentioned core module as a dependency.
 A typical workflow would be the following. After enabling the new stack, the user would be in this situation:
+A typical workflow would be the following. After logging in, the user would be in this situation (note: the examples below were produced with the old Haswell stack):
 {{{
 …
 - `ml +module` (or `ml module`) allows to load a specific module (e.g. `ml Intel` loads the default version of the Intel module);
 - `ml -module` unloads the previously loaded module (e.g. `ml -Intel` removes the currently loaded version of the Intel module);
 - the `ml` wrapper can be user instead of `module` for all the subcommands of `module` (e.g. `ml avail` or `ml av`, or `ml restore`, etc.)
+- the `ml` wrapper can be used instead of `module` for all the subcommands of `module` (e.g. `ml avail` or `ml av`, or `ml restore`, etc.)
 More information on lmod can be found [https://lmod.readthedocs.io/en/latest/ here].