From a4b3f90a4603bf0adad1d3b51aae7a310f9d75df Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Wed, 31 Aug 2022 13:29:42 +0200
Subject: [PATCH] Link to section on job files

---
 doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

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 c742d8b33..bbade6249 100644
--- a/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md
+++ b/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md
@@ -213,7 +213,8 @@ There are three typical options for the use of workspaces:
 ### Per-Job Storage
 
 A batch job needs a directory for temporary data. This can be deleted afterwards.
-To help you to write your own (Slurm) job file, suited to your own needs, we came up with
+To help you to write your own [(Slurm) job file](../jobs_and_resources/slurm.md#job-files),
+suited to your own needs, we came up with
 the following example (which works [for the program g16](../software/nanoscale_simulations.md)).
 You will probably want to adjust it in a few places (e.g. what software you want to
 [load](../software/modules.md), inserting the path to your input file and actually
-- 
GitLab