From 700fbc1f50c8e29438fce73da049ae77dbf46713 Mon Sep 17 00:00:00 2001
From: Thomas Lynn Marcus <thomas_lynn.marcus@tu-dresden.de>
Date: Fri, 14 Oct 2022 15:00:31 +0200
Subject: [PATCH] make clear that typing `srun` does nothing

---
 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 7043d4604..057c1e459 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
@@ -79,7 +79,7 @@ There are three basic Slurm commands for job submission and execution:
 1. `salloc`: Obtain a Slurm job allocation (i.e., resources like CPUs, nodes and GPUs) for
 interactive use. Release the allocation when finished.
 
-Using `srun` directly on the shell will be blocking and launch an
+Executing a program with `srun` directly on the shell will be blocking and launch an
 [interactive job](#interactive-jobs). Apart from short test runs, it is recommended to submit your
 jobs to Slurm for later execution by using [batch jobs](#batch-jobs). For that, you can conveniently
 put the parameters in a [job file](#job-files), which you can submit using `sbatch
-- 
GitLab