WRF.md, updated VSC5 description

WRF.md

@@ -172,7 +172,9 @@ In general, compiled WRF versions are already available on all of our servers (S
 
 However, we describe the typical workflow of the compilation, for anyone that wishes to try it out. There are three steps: (i) make libraries available, (ii) configure, (iii) compile.
 
-* *Make the prerequisite libraries available*. In most cases, precompiled libraries can be made available to the operating system using environment modules. Environment modules modify the Linux shell environment so that the operating system is aware of where to find specific executable files, include files, software libraries, documentation files. Each server has its own set of available modules. As of 1.3.2023, WRF is known to compile and run with the following module collections.
+### Make the prerequisite libraries available
+
+In most cases, precompiled libraries can be made available to the operating system using environment modules. Environment modules modify the Linux shell environment so that the operating system is aware of where to find specific executable files, include files, software libraries, documentation files. Each server has its own set of available modules. As of 1.3.2023, WRF is known to compile and run with the following module collections.
 
 SRVX1:
 ```
@@ -227,13 +229,13 @@ However, we describe the typical workflow of the compilation, for anyone that wi
 NETCDF=/gpfs/opt/sw/spack-0.19.0/opt/spack/linux-almalinux8-skylake/intel-2021.5.0/netcdf-fortran-4.6.0-pnaropyoft7hicu7bfsugqa2aqcsggxj
 ```
 
-    On VSC5 do not use `module`, but spack:
+On VSC5 do not use `module`, but `spack`:
 ```
 spack load intel-oneapi-compilers
 spack load netcdf-fortran@4.4.5%intel
 ```
 
-    To check the libary paths of loaded modules:
+To check the library paths of loaded modules:
 ```
 (zen3) [serafins@l51 ~]$ spack find --loaded --paths
 ==> In environment zen3
@@ -258,7 +260,9 @@ However, we describe the typical workflow of the compilation, for anyone that wi
 
 Important note: **The environment must be consistent between compilation and runtime. If you compile WRF with a set of modules loaded, you must run it with the same set of modules**.
 
-* *Configure WRF for compilation.* This will test the system to check that all libraries can be properly linked. Type `./configure`, pick a generic dmpar INTEL (ifort/icc) configuration (usually 15), answer 1 when asked if you want to compile for nesting, then hit enter. "dmpar" means "distributed memory parallelization" and enables running WRF in parallel computing mode. For test compilations or for a toy setup, you might also choose a "serial" configuration.
+### Configure WRF for compilation
+
+This will test the system to check that all libraries can be properly linked. Type `./configure`, pick a generic dmpar INTEL (ifort/icc) configuration (usually 15), answer 1 when asked if you want to compile for nesting, then hit enter. "dmpar" means "distributed memory parallelization" and enables running WRF in parallel computing mode. For test compilations or for a toy setup, you might also choose a "serial" configuration.
 
 If all goes well, the configuration will end will a message like this:
 ```
@@ -291,7 +295,9 @@ However, we describe the typical workflow of the compilation, for anyone that wi
 
 The configure script stores the model configuration to a file called `configure.wrf`. This is specific to the source code version, to the server where the source code is compiled, and to the software environment. If you a have a working `configure.wrf` file for a given source code/server/environment, back it up.
 
-* *Compile WRF.* You always compile WRF for a specific model configuration. The ones we use most commonly are `em_les` (for large-eddy simulation), `em_quarter_ss` (for idealized mesoscale simulations), `em_real` (for real-case forecasts). So type either of the following, depending on what you want to get:
+### Compile WRF
+
+You always compile WRF for a specific model configuration. The ones we use most commonly are `em_les` (for large-eddy simulation), `em_quarter_ss` (for idealized mesoscale simulations), `em_real` (for real-case forecasts). So type either of the following, depending on what you want to get:
 ```
 ./compile em_les > compile.log 2>&1 &
 ./compile em_quarter_ss > compile.log 2>&1 &