harmonise the CWP and HPCP storage docs

Author: bcumming

docs/platforms/cwp/index.md

@@ -37,35 +37,30 @@ There are three main file systems mounted on the CWP system Santis.
 
 ### Home
 
-Every user has a home path (`$HOME`) mounted at `/users/$USER` on the [VAST][ref-alps-vast] filesystem.
+Every user has a [home][ref-storage-home] path (`$HOME`) mounted at `/users/$USER` on the [VAST][ref-alps-vast] filesystem.
 The home directory has 50 GB of capacity, and is intended for configuration, small software packages and scripts.
 
 ### Scratch
 
 The Scratch filesystem provides temporary storage for high-performance I/O for executing jobs.
-Use scratch to store datasets that will be accessed by jobs, and for job output.
-Scratch is per user - each user gets separate scratch path and quota.
 
-!!! info
-    A quota of 150 TB and 1 million inodes (files and folders) is applied to your scratch path.
+See the [Scratch][ref-storage-scratch] documentation for more information.
 
-    These are implemented as soft quotas: upon reaching either limit there is a grace period of 1 week before write access to `$SCRATCH` is blocked.
-
-    You can check your quota at any time from Ela or one of the login nodes, using the [`quota` command][ref-storage-quota].
-
-!!! info
-    The environment variable `SCRATCH=/capstor/scratch/cscs/$USER` is set automatically when you log into the system, and can be used as a shortcut to access scratch.
+The environment variable `SCRATCH=/capstor/scratch/cscs/$USER` is set automatically when you log into the system, and can be used as a shortcut to access scratch.
 
 !!! warning "scratch cleanup policy"
     Files that have not been accessed in 30 days are automatically deleted.
 
-    **Scratch is not intended for permanent storage**: transfer files back to the capstor project storage after job runs.
+    **Scratch is not intended for permanent storage**: transfer files back to the [Store][ref-storage-store] after job runs.
+
+### Project Store
 
-### Project
+Project storage is backed up, with no cleaning policy, as intermediate storage space for datasets, shared code or configuration scripts that need to be accessed from different vClusters.
 
-Project storage is backed up, with no cleaning policy: it provides intermediate storage space for datasets, shared code or configuration scripts that need to be accessed from different vClusters.
-Project is per project - each project gets a project folder with project-specific quota.
+The environment variable `PROJECT` is set automatically when you log into the system, and can be used as a shortcut to access the Store path for your primary project.
 
-* hard limits on capacity and inodes prevent users from writing to project if the quota is reached - you can check quota and available space by running the [`quota`][ref-storage-quota] command on a login node or ela.
-* it is not recommended to write directly to the project path from jobs.
+Hard limits on capacity and inodes prevent users from writing to [Store][ref-storage-store] if the quota is reached.
+You can check quota and available space by running the [`quota`][ref-storage-quota] command on a login node or ela.
 
+!!! warning
+    It is not recommended to write directly to the `$PROJECT` path from jobs.