added text about batch system and workspace for launchdirs

docs/advanced.rst

@@ -38,14 +38,21 @@ for the queing systems MOAB and SLURM see the examples provided in the folder
 
 In practical use cases, it is generally of advantage to separate the configuration
 files, the workflow templates (i.e. the input) and the launches. This structure
-is used in the demo 6 in folder **demos/6_advanced**.
+is used in folder **demos/6_advanced**.
 
 To submit a single fireworker batch job on bwUniCluster the ``qlaunch`` command
-is called like this::
+is called like this in the **launches** folder::
 
     cd launches
     qlaunch -q ../config/qadapter_uc1_vasp.yaml -w ../config/fworker_uc1_vasp.yaml singleshot
 
+The submitted batch jobs can be managed with the commands of your batch system.
+For example, for SLURM these are the ``squeue`` and the ``scontrol`` commands.
+The sample adapters are configured in such a way that all launch directories will
+be created there where the ``qlaunch`` command was executed. For large outputs
+and large temporary data the best place of **launches** and **config** folders
+is within a workspace of a high-throughput cluster file system.
+
 
 
 Deal with failures and crashes