diff --git a/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md b/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md
index 7e3049bca90705b4a74644d030490306bef6527d..515628fb9be4aeb3ce5d01ef928026b521be5832 100644
--- a/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md
+++ b/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md
@@ -283,7 +283,7 @@ It performs the following steps once per day and filesystem:
 ### Restoring Expired Workspaces
 
 At expiration time your workspace will be moved to a special, hidden directory. For a month (in
-warm_archive: 2 months), you can still restore your data into an existing workspace.
+warm_archive: 2 months), you can still restore your data **into an existing workspace**.
 
 !!! warning
 
diff --git a/doc.zih.tu-dresden.de/docs/data_transfer/datamover.md b/doc.zih.tu-dresden.de/docs/data_transfer/datamover.md
index 28aba7bbfdcec8411f6510061d509c949d128f34..52eb38531de1a52971b46960663c091a0df56879 100644
--- a/doc.zih.tu-dresden.de/docs/data_transfer/datamover.md
+++ b/doc.zih.tu-dresden.de/docs/data_transfer/datamover.md
@@ -1,4 +1,4 @@
-# Datamover - Data Transfer Inside ZIH Systems
+# Transfer Data Inside ZIH Systems with Datamover
 
 With the **Datamover**, we provide a special data transfer machine for transferring data with best
 transfer speed between the filesystems of ZIH systems. The Datamover machine is not accessible
diff --git a/doc.zih.tu-dresden.de/docs/data_transfer/export_nodes.md b/doc.zih.tu-dresden.de/docs/data_transfer/export_nodes.md
index b4a22c95e3193bc9ff1a7c43b107fe5f7f74f953..36cfb088dfb2865a25bdfab9f8c0c8ab644138b3 100644
--- a/doc.zih.tu-dresden.de/docs/data_transfer/export_nodes.md
+++ b/doc.zih.tu-dresden.de/docs/data_transfer/export_nodes.md
@@ -1,4 +1,4 @@
-# Export Nodes - Data Transfer to/from ZIH Systems
+# Transfer Data to/from ZIH Systems via Export Nodes
 
 To copy large data to/from ZIH systems, the so-called **export nodes** should be used. While it is
 possible to transfer small files directly via the login nodes, they are not intended to be used that
diff --git a/doc.zih.tu-dresden.de/docs/software/vampir.md b/doc.zih.tu-dresden.de/docs/software/vampir.md
index ee07d2f5babebace6809e9e2c7e384326f94409d..efbc0717fb00e1e889c16bc6ab18e8d7db51836b 100644
--- a/doc.zih.tu-dresden.de/docs/software/vampir.md
+++ b/doc.zih.tu-dresden.de/docs/software/vampir.md
@@ -74,15 +74,21 @@ Submitting slurm 30 minutes job (this might take a while)...
 ```
 
 This way, a job with a timelimit of 30 minutes and default resources is submitted. This might fit
-your needs. If not, please feel free to request a customized job running VampirServer, e.g.
+your needs. If not, please feel free to request a **customized job** running VampirServer, e.g.
 
 ```console
-marie@login$ vampirserver start --ntasks=8 --time=01:00:00 --mem-per-cpu=3000M --partition=romeo
+marie@login$ vampirserver start --ntasks=8 -- --time=01:00:00 -- --mem-per-cpu=3000M --partition=romeo
 Launching VampirServer...
 Submitting slurm 01:00:00 minutes job (this might take a while)...
 ```
 
-Above automatically allocates its resources via the respective batch system. If you want to start
+The above `vampirserver` command automatically allocates its resources via the respective batch
+system (, i.e. [Slurm](../jobs_and_resources/slurm.md) on ZIH systems). As shown, you can customize
+the resources requirements and time limit. This is especially useful, if you run into performance
+issues handling very large trace files. Please refer to `vampirserver --help` for further options
+and usage.
+
+If you want to start
 
 VampirServer without a batch allocation or from inside an interactive allocation, use
 
diff --git a/doc.zih.tu-dresden.de/util/check-toc-equals-page-headings.py b/doc.zih.tu-dresden.de/util/check-toc-equals-page-headings.py
index ec66904b419c857fb194a38daf47e1a5b4677bb1..75f85df0821772480c0ce78336250921c3614a03 100755
--- a/doc.zih.tu-dresden.de/util/check-toc-equals-page-headings.py
+++ b/doc.zih.tu-dresden.de/util/check-toc-equals-page-headings.py
@@ -1,6 +1,6 @@
-""" #!/usr/bin/env python
+#!/usr/bin/env python
+"""
 Check for consistency between TOC and page headings.
-Provide as an command line argument the path to the mkdocs.yml file.
 
 Author: Michael Bommhardt-Richter
 """
@@ -12,7 +12,7 @@ from pathlib import Path
 # {path/filename.md: [toc_heading, file_heading], ... }
 TOCData = dict()
 
-whitelist = ["index.md"]  # ["archive"]
+whitelist = ["index.md","archive/"]
 
 
 def get_heading_in_file(filename, docs_path):
@@ -52,11 +52,13 @@ def main():
         for key, value in TOCData.items():
             if key in whitelist:
                 continue
+            if whitelist[1] in key:
+                continue
             if value[0] == "Overview":
                 continue
             if value[0] != value[1]:
                 cnt += 1
-                print(f"{key:<40}{value[0]:<30} != {value[1]}")
+                print(f"{key:<40}{value[0]:<50} != {value[1]}")
         sys.exit(cnt)
     else:
         print("Error: Could not find mkdocs.yml file.")