Minor style fixes

Author: jluethi

docs/image_list.md

@@ -2,7 +2,7 @@
 layout: default
 ---
 
-# Image List
+# Fractal Image List
 
 While applying a processing workflow to a given dataset, Fractal keeps a list of all the OME-Zarr images it is processing and their metadata. In this page we describe the concepts of [images](#images) and [filters](#filters) - see also the [examples section](#examples).
 

docs/tasks_spec.md

@@ -2,7 +2,7 @@
 layout: default
 ---
 
-# Tasks
+# Fractal Tasks Specification
 
 Fractal tasks are modular and interoperable processing units that handle data in OME-Zarr containers. Each task is an executable that runs on a single OME-Zarr image or a collection of OME-Zarr images. In Fractal, we the OME-Zarrs to be processed by giving the tasks the zarr_urls(s), the paths to a given OME-Zarr image on disk or in the cloud. All tasks load data from an OME-Zarr on disk and store their processing results in an OME-Zarr (the same or a new one) on disk again. The parameters and metadata of tasks are described in a [Fractal manifest in json form](#task-list-and-manifest). This page contains an overview of the Fractal task specification, the [types of Fractal tasks](#task-types), the [manifest](#task-list-and-manifest) that specifies task metadata as well as their [input](#input-api) & [output](#output-api) API.
 

mkdocs.yml

@@ -43,11 +43,11 @@ plugins:
 
 nav:
   - Fractal: index.md
-  - Fractal tasks: fractal_tasks.md
-  - Fractal task spec: tasks_spec.md
+  - Fractal Tasks: fractal_tasks.md
+  - Fractal Task Spec: tasks_spec.md
   - Create a Fractal Task: build_your_own_fractal_task.md
   - Fractal Image List: image_list.md
-  - Deploy Fractal Server & Web: run_fractal.md
+  - Deploy Fractal: run_fractal.md
 
 
 # Include some page, without including them in the ToC