From 267665d06e83588082b54a9c8b2499508fd94b59 Mon Sep 17 00:00:00 2001
From: lazariv <taras.lazariv@tu-dresden.de>
Date: Fri, 20 May 2022 13:34:27 +0000
Subject: [PATCH] Improve language

---
 doc.zih.tu-dresden.de/docs/contrib/content_rules.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc.zih.tu-dresden.de/docs/contrib/content_rules.md b/doc.zih.tu-dresden.de/docs/contrib/content_rules.md
index b679565d5..9312a9cab 100644
--- a/doc.zih.tu-dresden.de/docs/contrib/content_rules.md
+++ b/doc.zih.tu-dresden.de/docs/contrib/content_rules.md
@@ -368,7 +368,7 @@ This should help to avoid errors.
 | `julia` partition      | `marie@julia$`   |
 | `dcv` partition        | `marie@dcv$`     |
 
-* **Always use a prompt**, even there is no output provided for the shown command.
+* **Always use a prompt**, even if there is no output provided for the shown command.
 * All code blocks which specify some general command templates, e.g. containing `<` and `>`
   (see [placeholders](#placeholders) and [unix rules](#unix-rules)), should use `bash` for the code
   block. Additionally, an example invocation, perhaps with output, should be given with the normal
@@ -380,7 +380,7 @@ This should help to avoid errors.
 #### Long Options
 
 The general rule is to provide long over short parameter names where possible to ease
-understanding. This holds especially for Slurm options, but also for other commands.
+understanding. This holds especially for Slurm options, but also other commands.
 
 ??? example
 
-- 
GitLab