Merge pull request #66 from hpc-unibe-ch/64-update-scratch-documentation

Update scratch documentation

docs/file-system/scratch.md

@@ -1,5 +1,9 @@
 Scratch - temporary file space
 
+!!! warning
+ Scratch serves as a temporary repository for compute output and is explicitly designed for short-term usage. Unlike other storage locations, scratch is not backed.
+ Files are subject to automatic removal if they are not accessed within a timeframe of 30 days.
+
 ## Description
 
 Scratch file space are meant for temporary data storage. Interim computational data should be located there. 
@@ -8,7 +12,7 @@ We distinguish local and network scratch spaces.
 ## Network Scratch
 Network scratch spaces are located on the parallel file system and accessible to all nodes. In contrast to `HOME` or `WORKSPACEs`, scratch is meant for temporary data, especially with larger quota requirements. 
 Jobs creating a lot of temporary data, which may need or may not need to be post-processed should run in this space. As an example, a application creating a huge amount of temporary output, which need to be analysed, but only partly need to be stored for a longer term.
-Quota and file quota is less restrictive on scratch compared to `HOME` or permanent `WORKSPACE` directories. Every user can use up to **30TB** and **10M** files. There is **no snapshot** and **no backup** feature available. Furthermore, an **automatic deletion policy** is planned, deleting files which are older than **30 days**. 
+Block and file quota is less restrictive on scratch compared to `HOME` or permanent `WORKSPACE` directories. Every user can use up to **30TB** and **10M** files. There is **no snapshot** and **no backup** feature available. Furthermore, an **automatic deletion policy** is implemented, deleting files which are older than **30 days**. Files are subject to automatic removal only if they are not accessed within a timeframe of 30 days. Any file with an access timestamp within the last 30 days remains exempt from the policy, ensuring that actively utilized files are not inadvertently affected.
 
 Scratch file space can be accessed using the Workspace module and the `$SCRATCH` environment variable.