From a23ef5b7199363f18ac2e49399ddfb10dccf68aa Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Tue, 5 Nov 2024 11:00:11 +0100
Subject: [PATCH] Apply 1 suggestion(s) to 1 file(s)
Co-authored-by: Bert Wesarg <bert.wesarg@tu-dresden.de>
---
doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md b/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md
index 6561497a9..66fcbf7d8 100644
--- a/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md
+++ b/doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md
@@ -364,7 +364,7 @@ expiration date in Unix timestamp format is added to the workspace name.
When you release a workspace **manually**, it will not receive a grace period and be
**permanently deleted** the **next day**. The advantage of this design is that you can create
- and release workspaces inside jobs and not flood the filesystem with data no one needs anymore
+ and release workspaces inside jobs and not pollute the filesystem with data no one needs anymore
in the hidden directories (when workspaces are in the grace period).
#### Expire Process
--
GitLab