diff --git a/Dedicated-Server-Guide-[WIP].md b/Dedicated-Server-Guide-[WIP].md
index 0f3d7f9..ffb0eef 100644
--- a/Dedicated-Server-Guide-[WIP].md
+++ b/Dedicated-Server-Guide-[WIP].md
@@ -62,9 +62,9 @@ You should also make the modification to the original file in DCS folder (see pr
 
 The dcs-liberation script will try and write the `state.json` file at the following locations :
 
-- %LIBERATION_EXPORT_DIR% (an environment variable)
+- `%LIBERATION_EXPORT_DIR%` (an environment variable)
 - the dcs-liberation install folder, stored in the mission (probably not the same on the server and on the computer that generated the mission)
-- the system's temporary folder (as defined in the %TEMP% environment variable)
+- the system's temporary folder (as defined in the `%TEMP%` environment variable)
 - DCS' install directory
 
 This will be stated in the DCS log file (accessible in `<saved games>\dcs\logs\dcs.log`) like this :
@@ -73,7 +73,33 @@ This will be stated in the DCS log file (accessible in `<saved games>\dcs\logs\d
 2020-10-20 20:44:52.652 INFO    SCRIPTING: DCSLiberation|87: DCS Liberation state will be written as json to [[D:\dev\_VEAF\dcs_liberation\state.json]]
 ```
 
+You can (and should) set the `%LIBERATION_EXPORT_DIR%` environment variable on your server. Please note that you'll have to restart DCS, and maybe even your server, depending on your configuration, before it's taken into account.
+
 ## Preparing the mission
 
+After installing dcs-liberation on a computer (let's call it the mission computer), configure it the way you like (including plugins, if you want), and start a new campaign.
+
+At one point, you'll want to *fly* a mission. When you press the *Take off* button in dcs-liberation, it'll generate a mission : `<saved games>\dcs\missions\liberation_nextturn.miz`.
+
+At the moment, it is mandatory to open the mission in the mission editor (on the mission computer), and save it. 
+
+**If you skip this step, the mission will not be playable on a dedicated DCS server !**
+
+
+Now, you can simply copy the mission file to your server and run it.
+
 ## Getting the result of the mission
 
+During the mission (at runtime, as we developers like to say), the state of the mission (destroyed units, captured bases) is written in the `state.json` file.
+
+It should be updated whenever a destruction or capture event occurs. But sometimes this doesn't work, so you have to be careful.
+
+When the mission is over, double-check that the `state.json` file is updated : check the file date, and if you dare, check its content.
+
+If in doubt, end the mission on the server (running another mission is enough ; I keep one "empty" mission on each theater, it's very quick to run).
+
+Then download the `state.json` file on the mission computer, and enter it in dcs-liberation, using the "Manually submit" button :
+
+![](https://i.imgur.com/Izml39p.jpg)
+
+If the "Waiting for mission completion" window is not visible anymore (you may have closed it, or the program), simply click the "Take off" button again.
\ No newline at end of file