From 44b09cec2b909262ef10ecbebdaf3b8cbcb1292c Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Tue, 14 Sep 2021 17:12:28 +0200
Subject: [PATCH] Fix wording

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

diff --git a/doc.zih.tu-dresden.de/docs/data_lifecycle/lustre.md b/doc.zih.tu-dresden.de/docs/data_lifecycle/lustre.md
index 891808543..d08a5d5f5 100644
--- a/doc.zih.tu-dresden.de/docs/data_lifecycle/lustre.md
+++ b/doc.zih.tu-dresden.de/docs/data_lifecycle/lustre.md
@@ -1,11 +1,11 @@
-# Lustre File System(s)
+# Lustre Filesystems
 
 ## Large Files in /scratch
 
 The data containers in [Lustre](https://www.lustre.org) are called object storage targets (OST). The
 capacity of one OST is about 21 TB. All files are striped over a certain number of these OSTs. For
 small and medium files, the default number is 2. As soon as a file grows above ~1 TB it makes sense
-to spread it over a higher number of OSTs, e.g. 16. Once the file system is used >75%, the average
+to spread it over a higher number of OSTs, e.g. 16. Once the filesystem is used >75%, the average
 space per OST is only 5 GB. So, it is essential to split your larger files so that the chunks can be
 saved!
 
-- 
GitLab