fix number of extension

number of extension for scratch and ssd where mixed up

Closes #182 (closed)

doc.zih.tu-dresden.de/docs/data_lifecycle/workspaces.md

@@ -102,15 +102,15 @@ maximum durations. A workspace can be extended multiple times, depending on the
 
 | Storage system (use with parameter -F ) | Duration, days | Extensions | Remarks |
 |:------------------------------------------:|:----------:|:-------:|:---------------------------------------------------------------------------------------:|
-| `ssd`                                       | 30 | 10 | High-IOPS filesystem (`/lustre/ssd`) on SSDs.                                          |
+| `ssd`                                       | 30 | 2 | High-IOPS filesystem (`/lustre/ssd`) on SSDs.                                          |
 | `beegfs`                                     | 30 | 2 | High-IOPS filesystem (`/lustre/ssd`) onNVMes.                                          |
-| `scratch`                                    | 100 | 2 | Scratch filesystem (/scratch) with high streaming bandwidth, based on spinning disks |
+| `scratch`                                    | 100 | 10 | Scratch filesystem (`/scratch`) with high streaming bandwidth, based on spinning disks |
 | `warm_archive`                               | 365 | 2 | Capacity filesystem based on spinning disks                                          |
 
 To extend your workspace use the following command:
 
 ```
-zih$ ws_extend -F scratch test-workspace 100      #extend the workspace for 100 days
+marie@login$ ws_extend -F scratch test-workspace 100      #extend the workspace for 100 days
 Info: extending workspace.
 /scratch/ws/marie-test-workspace
 remaining extensions  : 1
@@ -146,15 +146,15 @@ warm_archive: 2 months), you can still restore your data into an existing worksp
 
 Use:
 
-```
-ws_restore -l -F scratch
+```console
+marie@login$ ws_restore -l -F scratch
 ```
 
 to get a list of your expired workspaces, and then restore them like that into an existing, active
 workspace 'new_ws':
 
-```
-ws_restore -F scratch marie-test-workspace-1234567 new_ws
+```console
+marie@login$ ws_restore -F scratch marie-test-workspace-1234567 new_ws
 ```
 
 The expired workspace has to be specified by its full name as listed by `ws_restore -l`, including
@@ -198,7+198,7 @@
     #SBATCH --ntasks=1
     #SBATCH --cpus-per-task=24
 
     module load modenv/classic
     module load gaussian
 
     COMPUTE_DIR=gaussian_$SLURM_JOB_ID
@@ -218,7+218,7 @@
 For a series of jobs or calculations that work on the same data, you should allocate a workspace
 once, e.g., in `scratch` for 100 days:
 
-```
-zih$ ws_allocate -F scratch my_scratchdata 100
+```console
+marie@login$ ws_allocate -F scratch my_scratchdata 100
 Info: creating workspace.
 /scratch/ws/marie-my_scratchdata
 remaining extensions  : 2
@@ -234,8 +234,8 @@ chmod g+wrx /scratch/ws/marie-my_scratchdata
 
 And verify it with:
 
-```
-zih $ ls -la /scratch/ws/marie-my_scratchdata
+```console
+marie@login$ ls -la /scratch/ws/marie-my_scratchdata
 total 8
 drwxrwx--- 2 marie    hpcsupport 4096 Jul 10 09:03 .
 drwxr-xr-x 5 operator adm        4096 Jul 10 09:01 ..
@@ -247,8 +247,8 @@ For data that seldom changes but consumes a lot of space, the warm archive can b
 this is mounted read-only on the compute nodes, so you cannot use it as a work directory for your
 jobs!
 
-```
-zih$ ws_allocate -F warm_archive my_inputdata 365
+```console
+marie@login$ ws_allocate -F warm_archive my_inputdata 365
 /warm_archive/ws/marie-my_inputdata
 remaining extensions  : 2
 remaining time in days: 365
@@ -261,8 +261,8 @@ remaining time in days: 365
 
 To see your active quota use:
 
-```
-qinfo quota /warm_archive/ws/
+```console
+marie@login$ qinfo quota /warm_archive/ws/
 ```
 
 Note that the workspaces reside under the mountpoint `/warm_archive/ws/` and not `/warm_archive`