From a85c341c271c1377b022704d6969404039aee0ea Mon Sep 17 00:00:00 2001
From: Danny Rotscher <danny.rotscher@tu-dresden.de>
Date: Tue, 6 Dec 2022 15:39:23 +0100
Subject: [PATCH] Changed multithreading

---
 .../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 1b5bab624..695faedc5 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
@@ -71,7 +71,7 @@ The available compute nodes are grouped into logical (possibly overlapping) sets
 **partitions**. You can submit your job to a certain partition using the Slurm option
 `--partition=<partition-name>`.
 
-Some nodes have multithreading (SMT) enabled, so for every physical core allocated
+Some nodes have Multithreading (SMT) enabled, so for every physical core allocated
 (e.g., with `SLURM_HINT=nomultithread`), you will always get `MB per Core`*`number of threads`,
 because the memory of the other threads is allocated implicitly, too.
 
-- 
GitLab