From b4276b35c8b747ae49d227926d3ce6dd76fbb7fb Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Thu, 2 Nov 2023 09:16:05 +0100
Subject: [PATCH] Lint: Fix line lenght

---
 .../docs/software/singularity_recipe_hints.md             | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc.zih.tu-dresden.de/docs/software/singularity_recipe_hints.md b/doc.zih.tu-dresden.de/docs/software/singularity_recipe_hints.md
index c1f570c93..ab20fff41 100644
--- a/doc.zih.tu-dresden.de/docs/software/singularity_recipe_hints.md
+++ b/doc.zih.tu-dresden.de/docs/software/singularity_recipe_hints.md
@@ -195,10 +195,10 @@ This image may be run with
 singularity exec xeyes.sif xeyes.
 ```
 
-This works because all the magic is done by Singularity already like setting `${DISPLAY}` to the outside
-display and mounting `${HOME}` so `${HOME}/.Xauthority` (X11 authentication cookie) is found. When you are
-using `--contain` or `--no-home` you have to set that cookie yourself or mount/copy it inside
-the container. Similar for `--cleanenv` you have to set `${DISPLAY}`, e.g., via
+This works because all the magic is done by Singularity already like setting `${DISPLAY}` to the
+outside display and mounting `${HOME}` so `${HOME}/.Xauthority` (X11 authentication cookie) is
+found. When you are using `--contain` or `--no-home` you have to set that cookie yourself or
+mount/copy it inside the container. Similar for `--cleanenv` you have to set `${DISPLAY}`, e.g., via
 
 ```console
 export SINGULARITY_DISPLAY=${DISPLAY}
-- 
GitLab