From b1ea04af86bc9a944897e88151b116b7f7bf48df Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Sebastian=20D=C3=B6bel?= <sebastian.doebel@tu-dresden.de>
Date: Mon, 4 Nov 2024 13:29:04 +0100
Subject: [PATCH] Apply 1 suggestion(s) to 1 file(s)

Co-authored-by: Jan Frenzel <jan.frenzel@tu-dresden.de>
---
 doc.zih.tu-dresden.de/docs/data_lifecycle/permanent.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/doc.zih.tu-dresden.de/docs/data_lifecycle/permanent.md b/doc.zih.tu-dresden.de/docs/data_lifecycle/permanent.md
index e5f7a3359..840be0404 100644
--- a/doc.zih.tu-dresden.de/docs/data_lifecycle/permanent.md
+++ b/doc.zih.tu-dresden.de/docs/data_lifecycle/permanent.md
@@ -31,8 +31,9 @@ submit jobs into the batch system. Running jobs are not affected.
      We have no feasible way to get the contribution of
      a single user to a project's disk usage.
 
-Because of the quota, it is recommended not to store cache data, which is automatically
-created by some applications or frameworks, in `/tmp` or in workspaces.
+Some applications and frameworks are known to store cache or temporary data at places where quota
+applies. You can change the default places using environment variables. We suggest to put such data
+in `/tmp` or workspaces.
 We cannot list all applications that do this, but some known ones are
 
 | Application      | Environment variable              |
-- 
GitLab