From 2e46cf197cb59fa1cd9eaa48904db1699a3d6427 Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Wed, 19 Oct 2022 08:52:46 +0200
Subject: [PATCH] Apply 1 suggestion(s) to 1 file(s)

---
 .../docs/jobs_and_resources/partitions_and_limits.md            | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc.zih.tu-dresden.de/docs/jobs_and_resources/partitions_and_limits.md b/doc.zih.tu-dresden.de/docs/jobs_and_resources/partitions_and_limits.md
index 50920ca6a..ae450f8b4 100644
--- a/doc.zih.tu-dresden.de/docs/jobs_and_resources/partitions_and_limits.md
+++ b/doc.zih.tu-dresden.de/docs/jobs_and_resources/partitions_and_limits.md
@@ -62,7 +62,7 @@ Memory requirements for your job can be specified via the `sbatch/srun` paramete
 of the partition it runs on is quite low at **300 MB** per CPU. If you need more memory, you need
 to request it.
 
-ZIH system comprises different sets of nodes with different amount of installed memory which affect
+ZIH systems comprise different sets of nodes with different amount of installed memory which affect
 where your job may be run. To achieve the shortest possible waiting time for your jobs, you should
 be aware of the limits shown in the following table.
 
-- 
GitLab