Minors.

e0_performance-studies.tex

@@ -156,13 +156,15 @@ with just another parser subprogram:
 
 \subsection{Example: ElasticWave3D - shared memory scalability}
 
-Below you find an example of an comprehensive performance study examining the multi-core
+Below you will find files used for an comprehensive performance study examining the multi-core
 scalability of the linear ADER-DG application \texttt{ElasticWave3D} \\
 (path: \texttt{ApplicationExamples}\texttt{/Linear/ElasticWave3D}).
 The example is used to detail the sections of the configuration file
-and to show an example of a job script and a specification file template.
+and to show examples of the job script template and the specification file template.
+The configuration file has the structure of an INI file and is processed
+by python3's built-in INI file parser.
 
-The test varies the number of cores (and background job consumer tasks), the polynomial order,
+The performance study varies the number of cores (and background job consumer tasks), the polynomial order,
 the ADER-DG implementation (``fused'' vs. ``nonfused''), if predictor background jobs are used, if
 update background jobs are used, if zero or two levels of AMR should be used, and so on ...
 The parameter keys and their associated list of values can be specified as
@@ -182,12 +184,12 @@ or as a single key with a mix of quoted and unquoted values:
 \begin{code}
 <key> = "<value0>",<value1>,"<value2>"
 \end{code}
-We span the parameter space as a Cartesian product of the single
+The parameter space is spanned as a Cartesian product of the single
 parameter key-value list combinations. 
-A parameter key is a dimension in the parameter space.
+Each parameter key is a dimension in the parameter space.
 Different values for a certain parameter key are separated by commas (',').
 You can further put parameter values in quotation marks ('"') if a parameter
-contains commas itself or to prevent trimming of leading or trailing whitespaces.
+contains commas itself or in order to prevent trimming of leading or trailing whitespaces.
 
 For each parameter combination, one experiment will be performed. 
 Elements of the parameter space may be directly mapped to a job script or whole subspaces may be 
@@ -197,13 +199,15 @@ a job script, the parameters in \texttt{parameters\_grouped} are grouped onto th
 It is further possible to prescribe and vary environment variables.
 For each different configuration of environment variables,
 a new executable is created.
-This prevents you from accidentally using a different compiler when rerunnin an experiment.
-You specify environment variables exactly in the same way as parameters.
+This prevents you from accidentally using a different compiler or build mode when rerunning 
+an experiment. You specify environment variables exactly in the same way as parameters.
 
-The workflow from which extracted the scripts below assumes that the script is placed 
+The workflow from which we extracted the files below assumes that the script is placed 
 into the project folder. For convenience, we typically symlink \texttt{Benchmarks/python/sweep.py}
 into the project folder, too.
 
+The configuration file used for performance study is given below.
+Comments start with an ';' or '#' symbol.
 \begin{code}
 [general]
 exahype_root   = <mypath>/ExaHyPE-Engine