fixed spaces and version in installation episode

Author: rswamina

_episodes/02-installation.md

@@ -229,10 +229,13 @@ to display the command line help.
 > > {: .bash}
 > > The version of ESMValTool installed should be displayed on the screen as:
 > > ~~~
-> > ESMValCore: 2.6.0
-> > ESMValTool: 2.6.0
+> > ESMValCore: 2.8.0
+> > ESMValTool: 2.8.0
 > > ~~~
 > > {: .output}
+> Note that on HPC servers such as JASMIN, sometimes a more recent development 
+> version may be displayed for ESMValTool, for e.g. 
+> `ESMValTool: 2.9.0.dev4+g6948d5512`
 > {: .solution}
 {: .challenge}
 

_episodes/04-recipe.md

@@ -362,11 +362,11 @@ Do you recognize the basic recipe structure that was introduced in episode 1?
 >>    form of `.xml` files.
 > > - **timeseries/tas_global**: creates `/preproc/timeseries/tas_global`, which
 > >   contains preprocessed data for each of the input datasets, a
-> >   `metadata.yml` file and provenance information in the 
+> >    `metadata.yml` file and provenance information in the 
 >>    form of `.xml` files.
 > > - **timeseries/tas_amsterdam**: creates `/preproc/timeseries/tas_amsterdam`,
 > >   which contains preprocessed data for each of the input datasets, plus a
-> >   combined `MultiModelMean`, a`metadata.yml` file and provenance files.
+> >   combined `MultiModelMean`, a `metadata.yml` file and provenance files.
 > > - **map/script1**: creates `/run/map/script1` with general information and a
 > >   log of the diagnostic script run. It also creates `/plots/map/script1` and
 > >   `/work/map/script1`, which contain output figures and output datasets,