From a5ede84483c6a2f8dccb80f5adcda6af7612ad59 Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Tue, 27 Sep 2022 16:00:09 +0200
Subject: [PATCH] Apply 1 suggestion(s) to 1 file(s)

---
 doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

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 da9d7e67d..4b6474efd 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
@@ -85,7 +85,7 @@ 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, which is stored in the environment variable
+After submission, 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.
-- 
GitLab