Updated for JADE2

jade/modules.rst

@@ -25,24 +25,24 @@ The utility displays the available modules by issuing the command::
 
 or displays only the information related to a certain software package, *e.g.*::
 
-  module avail pgi
+  module avail gromacs
 
 The avail instruction displays all the versions available for the installed applications, and shows which version is pre-defined as being the default. A software package is loaded with the load or the add instructions, *e.g.*::
 
-  module load pgi
+  module load gromacs
 
 If no version is specified, the default version of the software is loaded. Specific versions, other than the default can be loaded by specifying the version, *e.g.*::
 
-  module load pgi/2017
+  module load gromacs/2020.3
 
 The modules that are already loaded by users in a session are displayed with the command::
 
   module list
 
 A module can be "unloaded" with the unload or rm instructions, *e.g.*::
 
-  module unload pgi
-  module load pgi/2017
+  module unload gromacs
+  module load gromacs/2020.3
 
 Lastly, all modules loaded in a session can be "unloaded" with a single command:::
 
@@ -55,4 +55,4 @@ Best practices
 ``module`` can be used to modify the environment after login, *e.g.* to load the Portland compilers in order to build an application.  However, most frequent usage will be to load an already built application, and the best way to do this is from within the submission script.  For example, assuming a job uses the NAMD molecular dynamics package, the submission script contains::
 
   module purge
-  module load NAMD
+  module load namd