More docs

docs/source/available_notebooks.rst

-.. available_notebooks:
+.. _available_notebooks:
 
 Available Notebooks
 ===================

docs/source/how_it_works.rst

@@ -7,7 +7,7 @@ to expose Jupyter_ notebooks to a command line interface.
 Additionally, it leverages the DESY/XFEL Maxwell cluster to run these jobs in parallel
 via SLURM_.
 
-Here is a list of `available notebooks`_.
+Here is a list of `Available Notebooks`_.
 
 .. _nbparameterise: https://github.com/takluyver/nbparameterise
 .. _nbconver: https://github.com/jupyter/nbconvert

docs/source/index.rst

@@ -11,9 +11,11 @@ Contents:
 .. toctree::
    :maxdepth: 2
    
+   how_it_works
    installation
    configuration
    workflow
+   availabe_notebooks
 
 
 

docs/source/installation.rst

@@ -39,5 +39,5 @@ all prerequisites and this tool chain by running::
 
     pip install -r requirements.txt .
     
-After installation, you should adjust the configuration_ and settings to
+After installation, you should adjust the :ref:`configuration` and settings to
 match your environment.
\ No newline at end of file

docs/source/workflow.rst

@@ -294,7 +294,7 @@ launch a concurrent job and generate a report out of notebook. If it fails to ru
 normal Jupyter notebook environment, it will certainly fail in the tool chain environment.
 
 Once you are satisfied with your current state of initial development, you can add it
-to the list of notebooks as mentioned in the configuration_ section.
+to the list of notebooks as mentioned in the :ref:`configuration` section.
 
 Any changes you now make in the notebook will be automatically propagated to the command line.
 Specifically, you should verify that all arguments are parsed correctly, e.g. by calling::