From 91763119ff199791f457bb815a8fff3d5e2651e3 Mon Sep 17 00:00:00 2001
From: Stefano Serafin <stefano.serafin@univie.ac.at>
Date: Fri, 17 Mar 2023 08:08:27 +0000
Subject: [PATCH] typos

---
 WRF.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/WRF.md b/WRF.md
index db2d22a..b6a3750 100644
--- a/WRF.md
+++ b/WRF.md
@@ -74,7 +74,7 @@ ln -s $WPS_PATH/met_em* .
 ./wrf.exe
 ```
 
-The `met_em*` files linked in this snipped are the outcome of the WRF preprocessing (interpolation of initial and boundary conditions from another model, or from reanalyses, on the WRF grid). The WRF preprocessing system (WPS) is a separate set of executables, that can be built only after WRF is successfully compiled. To run WPS for a real-case simulation, getting initial and boundary conditions from ECMWF-IFS data on model levels, you could use a script such as the following. However, it depends on namelists, variable tables and other settings files being correctly specified. See below for details.
+The `met_em*` files linked in this snippet are the outcome of the WRF preprocessing (interpolation of initial and boundary conditions from another model, or from reanalyses, on the WRF grid). The WRF preprocessing system (WPS) is a separate set of executables, that can be built only after WRF is successfully compiled. To run WPS for a real-case simulation, getting initial and boundary conditions from ECMWF-IFS data on model levels, you could use a script such as the following. However, it depends on namelists, variable tables and other settings files being correctly specified. See below for details.
 
 ```sh title="Example: wrf-run-script.sh"
 #!/bin/bash
-- 
GitLab