From 7857afafe38d9b487cfe6d3eab6dbccc29ea2020 Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Tue, 27 Sep 2022 15:43:08 +0200
Subject: [PATCH] Resolve issue

---
 doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md b/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md
index 275d16edb..a31f40614 100644
--- a/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md
+++ b/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md
@@ -86,8 +86,9 @@ jobs to Slurm for later execution by using [batch jobs](#batch-jobs). For that,
 put the parameters in a [job file](#job-files), which you can submit using `sbatch
 [options] <job file>`.
 
-After submitting, your job gets a unique job id (stored in the environment variable `SLURM_JOB_ID`
-at runtime) which you can find via `squeue --me`. The id allows you to
+After submitting, your job gets a unique job ID, which is stored in the environment variable
+`SLURM_JOB_ID` at job runtime. The command `sbatch` outputs the job ID to stderr. Furthermore, you
+can find it via `squeue --me`. The job ID allows you to
 [manage and control](#manage-and-control-jobs) your jobs.
 
 !!! warning "srun vs. mpirun"
-- 
GitLab