diff --git a/WRF.md b/WRF.md
index 6c6305176d766df300169195ec4326a025513470..a18d6b97bebf9dcc2bf997c66f724608f37b2448 100644
--- a/WRF.md
+++ b/WRF.md
@@ -1,10 +1,12 @@
 # Table of contents
 
 1. [What is WRF](#what-is-wrf)
+1. [For the impatient](#for-the-impatient)
 1. [Basic usage](#basic-usage)
     * [Organization of the source code](#organization-of-the-source-code)
     * [Compiling the model](#compiling-the-model)
     * [Copying compiled WRF code](#copying-compiled-wrf-code)
+    * [Running WRF in a software container](#)
     * [Running an idealized simulation](#)
     * [Running a real-case simulation](#)
     * [Suggested workflow](#)
@@ -16,6 +18,7 @@
     * [Customizing model output](#)
     * [Adding namelist variables](#)
     * [Running offline nested simulations](#)
+    * [Running LES with online computation of resolved-fluxes turbulent fluxes](#)
 1. [Data assimilation (DA)](#)
     * [Observation nudging](#)
     * [Variational DA](#)
@@ -61,6 +64,10 @@ tar xzvf v4.4.2.tar.gz
 unzip v4.4.2.zip
 ```
 
+# For the impatient
+
+(quick overview of the compilation/simulation process, without details)
+
 # Basic usage
 
 ## Organization of the source code
@@ -191,7 +198,7 @@ However, we describe the typical workflow of the compilation, for anyone that wi
     ```
     The `> compile.log` tells the operating system to redirect the output stream from the terminal to a file called `compile.log`. The `2>&1` tells the operating system to merge the standard and error output streams, so `compile.log` will contain both regular output and error messages. The final `&` tells the operating system to run the job in the background, and returns to the terminal prompt.
 
-    The compiled code will be created in the `run` directory, and some of the compiled programs will be linked in either of the `test/em_les`, `test/em_quarter_ss` or `test/em_real` directories. Executable WRF files typically have names ending with `.exe` (this just conventional; it is actually not necessary for them to run).
+    The compiled code will be created in the `run` directory, and some of the compiled programs will be linked in either of the `test/em_les`, `test/em_quarter_ss` or `test/em_real` directories. Executable WRF files typically have names ending with `.exe` (this is just conventional; it is actually not necessary for them to run).
 
     Compilation may take half an hour or so. A successful compilation ends with:
     ```
@@ -221,6 +228,8 @@ However, we describe the typical workflow of the compilation, for anyone that wi
 
 ## Copying compiled WRF code
 
+## Running WRF in a software container
+
 ## Running an idealized simulation
 
 ## Running a real-case simulation
@@ -245,6 +254,10 @@ However, we describe the typical workflow of the compilation, for anyone that wi
 
 ## Running offline nested simulations
 
+## Running LES with online computation of resolved-fluxes turbulent fluxes
+
+WRFlux
+
 # Data assimilation (DA)
 
 ## Observation nudging