Documentation.md

@@ -233,10 +233,10 @@ Ramses replicates the filesystem setup of CHEOPS, specifically:
   - directory <user> is automatically created
   - automatic backup on [Commvault](https://www.commvault.com/) appliances
 - /scratch/\<user\>
-  - size per user 40TB
-  - create directory youself! (you _could_ use any name you like, but for clarity we recommend choosing your login-name.
-  - NO AUTOMATIC BACKUP, automatic deletion of files will be activated soon
-  - typical usage: input data should be copied to the scratch-partition only for running or soon running jobs. Accordingly, input and temporary data on /scratch should be deleted and output data transferred to longer term storage after job completion.
+  - size per user: 40TB
+  - create directory youself! (you _could_ use any name you like, but for clarity we recommend choosing your login-name)
+  - NO AUTOMATIC BACKUP, automatic deletion of files after 30 days
+  - typical usage: input data should be copied to the scratch partition only for running or soon running jobs. Accordingly, input and temporary data on /scratch should be deleted and output data transferred to longer term storage after job completion.
 - /project/\<user/group\>
   - created on request
   - NO AUTOMATIC BACKUP
@@ -277,7 +277,7 @@ There are several partitions/queues in slurm intended for general usage:
 - _ft-aurora_
   - a partition with a single node that contains two NEC SX Aurora Vector Engine Cards
 
-When a partition isn't explicitly specified with the “-p” parameter, the automatic routing mechanism determines the right partition for the job:
+If a partition is not explicitly specified with the "-p" parameter during job submission, the automatic routing mechanism determines the correct partition for the job:
 
 - "mpi" partition:
   - when the memory specification is core oriented (mem_per_cpu) and multiple tasks are specified
@@ -297,8 +297,8 @@ sacctmgr show assoc -n user=$USER format=Account
 
 `module` is a user interface to the Modules package, which allows the dynamic modification of the user's environment via module‐files. This helps avoid software conflicts due to incompatibilities, versioning, dependencies, etc. Further, module-files allow for concurrent usage of different software versions, for example, when cross-checking executable-output of new compiler versions.
 
-Your shell-initialization script can select frequently used modules. For example, an entry in your `~/.bashrc` file might look like this:  
-`module load lang/Julia/1.9.3-linux-x86_64 lang/Python/3.11.5-GCCcore-13.2.0  # load My Favorite Things`
+Your shell initialization script can select frequently used modules. For example, an entry in your `~/.bashrc` file might look like this:  
+`module load lang/Julia/1.9.3-linux-x86_64 lang/Python/3.11.5-GCCcore-13.2.0  # load my favorite programming languages`
 
 Basic `module` commands are:
 | Syntax | Description |