Merge branch 'main' into update_episode06_for_v2.9

Author: rswamina

_episodes/00-introduction.md

@@ -2,7 +2,7 @@
 title: "Introduction"
 teaching: 5
 exercises: 10
-compatibility: ESMValTool v2.8.0
+compatibility: ESMValTool v2.10.0
 
 questions:
 - What is ESMValTool?

_episodes/01-quickstart.md

@@ -2,7 +2,7 @@
 title: "Quickstart guide"
 teaching: 2
 exercises: 8
-compatibility: ESMValTool v2.8.0
+compatibility: ESMValTool v2.10.0
 
 questions:
 

_episodes/02-installation.md

@@ -2,7 +2,7 @@
 title: "Installation"
 teaching: 10
 exercises: 10
-compatibility: ESMValTool v2.8.0
+compatibility: ESMValTool v2.10.0
 questions:
 - "What are the prerequisites for installing ESMValTool?"
 - "How do I confirm that the installation was successful?"
@@ -229,8 +229,8 @@ to display the command line help.
 > > {: .bash}
 > > The version of ESMValTool installed should be displayed on the screen as:
 > > ~~~
-> > ESMValCore: 2.8.0
-> > ESMValTool: 2.8.0
+> > ESMValCore: 2.10.0
+> > ESMValTool: 2.10.0
 > > ~~~
 > > {: .output}
 > Note that on HPC servers such as JASMIN, sometimes a more recent development 

_episodes/03-configuration.md

@@ -2,7 +2,7 @@
 title: "Configuration"
 teaching: 10
 exercises: 10
-compatibility: ESMValTool v2.8.0
+compatibility: ESMValTool v2.10.0
 
 questions:
 - What is the user configuration file and how should I use it?
@@ -60,6 +60,8 @@ and then modify it if needed:
   nano ~/.esmvaltool/config-user.yml
 ~~~
 
+Any other editor can be used, e.g.vim.
+
 This file contains the information for:
 
 - Output settings

_episodes/04-recipe.md

@@ -2,7 +2,7 @@
 title: "Running your first recipe"
 teaching: 15
 exercises: 15
-compatibility: ESMValTool v2.8.0
+compatibility: ESMValTool v2.10.0
 
 questions:
 - "How to run a recipe?"
@@ -49,7 +49,7 @@ esmvaltool run --config_file ./config-user.yml examples/recipe_python.yml
 If everything is okay, you should see that ESMValTool is printing a lot of
 output to the command line. The final message should be "Run was successful".
 The exact output varies depending on your machine, but it should look something
-like the example output below.
+like the example log output on terminal below.
 
 {% include example_output.txt %}
 
@@ -132,7 +132,7 @@ distinguished in the log messages:
 > > following line in the output:
 > >
 > > ```
-> >[18776] INFO    These tasks will be executed: map/tas, timeseries/tas_global, 
+> >[134535] INFO    These tasks will be executed: map/tas, timeseries/tas_global, 
 >>timeseries/script1, map/script1, timeseries/tas_amsterdam
 > > ```
 > >
@@ -368,7 +368,7 @@ Do you recognize the basic recipe structure that was introduced in episode 1?
 > >   which contains preprocessed data for each of the input datasets, plus a
 > >   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
+> >   log of the diagnostic script run. It also creates `/plots/map/script1/` and
 > >   `/work/map/script1`, which contain output figures and output datasets,
 > >   respectively. For each output file, there is also corresponding provenance
 > >   information in the form of `.xml`, `.bibtex` and `.txt` files.

_episodes/05-conclusions.md

@@ -2,7 +2,7 @@
 title: "Conclusion of the basic tutorial"
 teaching: 10
 exercises: 0
-compatibility: ESMValTool v2.8.0
+compatibility: ESMValTool v2.10.0
 
 questions:
 - "What do I do now?"
@@ -69,32 +69,32 @@ to be suitable for use by ESMValTool.
 
 ### Where can I get more help?
 
-There are lots of resources available for helping you use ESMValTool.
+There are lots of resources available to assist you in using ESMValTool.
 
 The ESMValTool [Discussions page](https://github.com/ESMValGroup/ESMValTool/discussions)
-is a good place to learn about general issues, or to see if your question has
- been already addressed.
-If you have a GitHub account, you can also post your questions on the page.
+is a good place to find information on general issues, or check
+ if your question has already been addressed.
+If you have a GitHub account, you can also post your questions there.
 
-If you get stuck, a great starting point is to create a
-[new issue](https://github.com/ESMValGroup/ESMValTool/issues/new/choose). Note 
-that you will need a GitHub account for this.
+If you encounter difficulties, a great starting point is to visit issues page
+ [issue page](https://github.com/ESMValGroup/ESMValTool/issues) to check 
+whether your issues have already been reported or not. If they have been reported before,
+ suggestions provided by developers can help you to solve the issues you encountered.
+Note that you will need a GitHub account for this.
 
-There is also an ESMValTool email list.
+Additionally, there is an ESMValTool email list.
 Please see
-
-[information](https://docs.esmvaltool.org/en/latest/introduction.html#user-mailing-list)
-
-on how to subscribe to user mailing list.
+ [information](https://docs.esmvaltool.org/en/latest/introduction.html#user-mailing-list)
+ on how to subscribe to the user mailing list.
 
 ### What if I find a bug?
 
-If you find a bug, please report it back to the ESMValTool team.
-This will help us fix it, so that you can continue working,
-but also it means that ESMValTool will be more stable for everyone else as well.
+If you find a bug, please report it to the ESMValTool team.
+This will help us fix issues, ensuring not only your uninterrupted workflow
+ but also contributing to the overall stability of ESMValTool for all users.
 
 To report a bug, please create a new issue using the
-[new issue page](https://github.com/ESMValGroup/ESMValTool/issues/new/choose).
+[issue page](https://github.com/ESMValGroup/ESMValTool/issues).
 
 In your bug report, please describe the problem as clearly and as completely as possible.
 You may need to include a recipe or the output log as well.