Merge pull request #200 from ESMValGroup/change_chapter_order_v2

Change chapter order after the addition of advanced topic chapters

Author: Peter9192

_episodes/02-installation.md

@@ -40,7 +40,7 @@ After loading ``esmvaltool``, we can start using ESMValTool. Please see the [nex
 will tell you how!
 3. If you would like to start experimenting with existing diagnostics or contributing to ESMvalTool, please see the instructions for 
 source installation in the lesson [Development and
-contribution]({{ page.root }}{% link _episodes/08-development-setup.md %}) and
+contribution]({{ page.root }}{% link _episodes/07-development-setup.md %}) and
 in the [documentation](https://docs.esmvaltool.org/en/latest/quickstart/installation.html).
 
 > ## Install ESMValTool on Windows

_episodes/07-conclusions.md _episodes/05-conclusions.md_episodes/07-conclusions.md renamed to _episodes/05-conclusions.md

@@ -46,8 +46,8 @@ preprocessing, and then runs our Python script.
 
 > ## Drawing up a plan
 >
-> In the previous episode, we have seen that ESMValTool executed a number of
-> tasks. Write down which tasks we will need to do in this episode. And what does
+> Previously, we have seen that ESMValTool executed a number of
+> tasks. Write down which tasks we will need to do in this episode. And what do
 > each of these tasks do?
 >
 > > ## Answer
@@ -172,7 +172,7 @@ INFO    Run was successful
 ## Adding a dataset entry
 
 Let's add a datasets section. We will reuse the same datasets that we used in
-the previous episode. The data files are stored in `~/esmvaltool_tutorial/data`.
+previous episodes. The data files are stored in `~/esmvaltool_tutorial/data`.
 
 > ## Filling in the dataset keys
 >

_episodes/05-preprocessor.md _episodes/06-preprocessor.md_episodes/05-preprocessor.md renamed to _episodes/06-preprocessor.md

@@ -23,9 +23,9 @@ We now know how ESMValTool works, but how do we develop it?
 ESMValTool is an open-source project in ESMValGroup. We can contribute to its development by:
 
 - a new or updated recipe script, see lesson on
-[Writing your own recipe]({{ page.root }}{% link _episodes/05-preprocessor.md %})
+[Writing your own recipe]({{ page.root }}{% link _episodes/06-preprocessor.md %})
 - a new or updated diagnostics script, see lesson on
-[Writing your own diagnostic script]({{ page.root }}{% link _episodes/10-diagnostics.md %})
+[Writing your own diagnostic script]({{ page.root }}{% link _episodes/08-diagnostics.md %})
 - a new or updated cmorizer script, see lesson on
 [CMORization: Using observational datasets]({{ page.root }}{% link _episodes/09-cmorization.md %})
 - helping  with reviewing process of pull requests, see ESMValTool documentation on
@@ -214,7 +214,7 @@ Reviewing small incremental changes are more efficient.
 ### Background
 
 We saw 'warming stripes' in lesson
-[Writing your own recipe]({{ page.root }}{% link _episodes/05-preprocessor.md %}).
+[Writing your own recipe]({{ page.root }}{% link _episodes/06-preprocessor.md %}).
 Imagine the following task: you want to contribute warming stripes recipe and diagnostics
 to ESMValTool. You have to add the diagnostics
 [warming_stripes.py](../files/warming_stripes.py) and the recipe
@@ -372,7 +372,7 @@ when you submit a pull request.
 >> ~~~
 >>
 >> For details, see lesson
->> [Writing your own diagnostic script]({{ page.root }}{% link _episodes/10-diagnostics.md %}).
+>> [Writing your own diagnostic script]({{ page.root }}{% link _episodes/08-diagnostics.md %}).
 >>
 > {: .solution}
 {: .challenge}

_episodes/08-development-setup.md _episodes/07-development-setup.md_episodes/08-development-setup.md renamed to _episodes/07-development-setup.md

@@ -32,7 +32,7 @@ and writing Python diagnostics in this lesson.
 In this lesson, we will explain how to find an existing diagnostic and run it
 using ESMValTool installed in editable/development mode. For a development
 installation, see the instructions in the lesson [Development and
-contribution]({{ page.root }}{% link _episodes/08-development-setup.md %}).
+contribution]({{ page.root }}{% link _episodes/07-development-setup.md %}).
 Also, we will work with the recipe [recipe_python.yml][recipe] and the
 diagnostic script [diagnostic.py][diagnostic] called by this recipe that we have
 seen in the lesson [Running your first recipe]({{ page.root }}{% link

_episodes/10-diagnostics.md _episodes/08-diagnostics.md_episodes/10-diagnostics.md renamed to _episodes/08-diagnostics.md

@@ -60,7 +60,7 @@ that contains observations of the Gross Primary Production (GPP), a variable
 that is important for calculating components of the global carbon cycle.
 
 We will assume that you are using a development installation of ESMValTool as
-explained in the [previous episode](/08-development-setup).
+explained in the [Development and Contribution episode](/07-development-setup).
 
 
 ## Obtaining the data
@@ -224,7 +224,7 @@ CMORized, ESMValTool will give a warning or error.
 > >
 > > ```
 > >
-> > To learn more about writing a recipe, please refer to [Writing your own recipe](/05-preprocessor).
+> > To learn more about writing a recipe, please refer to [Writing your own recipe](/06-preprocessor).
 > >
 > {: .solution}
 {: .challenge}
@@ -745,8 +745,8 @@ utils.set_global_atts(cube, attributes)
 - **Make a pull request**. Since you have gone through all the trouble to
   reformat the dataset so that the ESMValTool can work with it, it would be
   great if you could provide the CMORizer, and ultimately with that the dataset,
-  to the rest of the community. For more information, see the previous episode
-  on [Contributing to ESMValTool](/08-development-setup).
+  to the rest of the community. For more information, see the episode
+  on [Development and contribution](/07-development-setup).
 
 - **Add documentation**. Make sure that you have added the info of your dataset
    to the User Guide so that people know it is available for the ESMValTool