From 1bcaa0c733425d2ff21b74f8bbb5a287a00c122f Mon Sep 17 00:00:00 2001
From: Sebastian Doebel <sebastian.doebel@tu-dresden.de>
Date: Tue, 16 Apr 2024 11:40:16 +0200
Subject: [PATCH] fix linting

---
 .../docs/jobs_and_resources/slurm_examples.md                  | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm_examples.md b/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm_examples.md
index c05c2da60..c7f8b1803 100644
--- a/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm_examples.md
+++ b/doc.zih.tu-dresden.de/docs/jobs_and_resources/slurm_examples.md
@@ -153,7 +153,8 @@ E.g., if you specify `--gres=gpu:2`, your total number of cores per node (meanin
 `ntasks`*`cpus-per-task`) may not exceed 12 on Alpha Centauri.
 
 Note that this also has implications for the use of the `--exclusive` parameter.
-Since this sets the number of allocated cores to the maximum, you also **must** request all GPUs otherwise your job will not start.
+Since this sets the number of allocated cores to the maximum, you also **must** request all GPUs 
+otherwise your job will not start.
 In the case of `--exclusive`, it won't be denied on submission,
 because this is evaluated in a later scheduling step.
 Jobs that directly request too many cores per GPU will be denied with the error message:
-- 
GitLab