Update project-storage.md

docs.it4i/storage/project-storage.md

@@ -6,8 +6,9 @@ The storage is intended to be used throughout the whole project's lifecycle.
 
 ## Technical Overview
 
-PROJECT storage consists of three equal file storages (blocks) called PROJ1, PROJ2 and PROJ3.
-Each file storage implements GPFS file system exported via NFS protocol using three NFS servers. File storages provide high-availability and redundancy.
+The PROJECT storage consists of three equal file storages (blocks) called PROJ1, PROJ2, and PROJ3.
+Each file storage implements GPFS file system exported via NFS protocol using three NFS servers.
+File storages provide high-availability and redundancy.
 
 **screenshot from DTS (draw.io?)**
 
@@ -20,16 +21,19 @@ Each file storage implements GPFS file system exported via NFS protocol using th
 
 ## Accessing PROJECT
 
-All aspects of allocation, provisioning, accessing and using PROJECT storage are driven by project paradigm.
+All aspects of allocation, provisioning, accessing, and using the PROJECT storage are driven by project paradigm.
 Storage allocation and access to the storage are based on projects (i.e. computing resources allocations) and project membership.
 
-Project directory (actually implemented as an independent fileset) is created for every active project. Default limits (quotas), default file permissions and ACLs are set. Project directory life cycle strictly follows project's life cycle. Project directory is removed after project's data expiration.
+A project directory (actually implemented as an independent fileset) is created for every active project.
+Default limits (quotas), default file permissions, and ACLs are set.
+The project directory life cycle strictly follows the project's life cycle.
+The project directory is removed after the project's data expiration.
 
 ### POSIX File Access
 
-PROJECT file storages are accessible at mountpoints `/mnt/proj1`, `/mnt/proj2` and `/mnt/proj3`.
+PROJECT file storages are accessible at mountpoints `/mnt/proj1`, `/mnt/proj2`, and `/mnt/proj3`.
 
-PROJECT storage can be accessed via the following nodes:
+The PROJECT storage can be accessed via the following nodes:
 
 | Cluster       | Node(s)                       |
 | ------------- | ----------------------------- |
@@ -46,14 +50,15 @@ $ it4i-get-project-dir OPEN-XX-XX
 
 ### Project Quotas
 
-The PROJECT storage enforces limits (quotas) on projects' usage (used capacity and allocated inodes), default quotas for capacity and amount of inodes per project are set by IT4Innovations.
+The PROJECT storage enforces limits (quotas) on projects' usage (used capacity and allocated inodes).
+Default quotas for capacity and amount of inodes per project are set by IT4Innovations.
 
 | Project default quota |        |
 | --------------------- | ------ |
 | Space quota           | 20TB   |
 | Inodes quota          | 5 mil. |
 
-Actual usage of the PROJECT storage (e.g. location of project directory, used capacity, allocated inodes) could be find in IT4Innovations' SCS information system, section Projects.
+Actual usage of the PROJECT storage (e.g. location of project directory, used capacity, allocated inodes) can be found in IT4Innovations' SCS information system, section Projects.
 
 ### Lifting Project Quotas
 
@@ -62,13 +67,13 @@ Alternatively, if the project is already active, contact [IT4I support][a].
 
 ### Snapshots
 
-PROJECT storage provides snapshot functionality. Snapshot represents a state of a filesystem at a particular point in time. Snapshots are created for all projects on fileset (i.e. project directory) level.
+The PROJECT storage provides snapshot functionality. A snapshot represents a state of a filesystem at a particular point in time. Snapshots are created for all projects on fileset (i.e. project directory) level.
 Snapshots are created every day, snaphots older than seven days are deleted.
 
-Files in snapshots are accessible directly by users in the special subdirectory of each project directory named ".snapshots".
+Files in snapshots are accessible directly by users in the special subdirectory of each project directory named `.snapshots`.
 Snapshots are read-only.
 
-Snapshots' names have format YYYY-MM-DD-hhmmss.
+Snapshots' names have the `YYYY-MM-DD-hhmmss` format.
 
 ```console
 [vop999@login1.salomon ~]# ls -al /mnt/proj3/open-XX-XX/.snapshots
@@ -86,7 +91,8 @@ drwxrws---. 16 vop999 open-XX-XX 4096 led 20 16:36 2021-03-07-021446
 
 ### ACL and File Permissions
 
-Access to project directory and containing files is restricted by Unix file permissions and file access control lists (ACLs). Default file permissions and ACLs are set by IT4Innovations during project directory provisioning.
+Access to a project directory and containing files is restricted by Unix file permissions and file access control lists (ACLs).
+Default file permissions and ACLs are set by IT4Innovations during project directory provisioning.
 
 nfs4 acl (link - the same info for all NFSv4 filesystems)
 
@@ -95,8 +101,8 @@ nfs4 acl (link - the same info for all NFSv4 filesystems)
 !!! note
     Data on the PROJECT storage is **not** backed up.
 
-
-PROJECT storage make use of fully redundant design, redundant devices, highly available services, data redundancy and snaphots, but does not provide backup of data.
+The PROJECT storage utilizes fully redundant design, redundant devices, highly available services, data redundancy, and snaphots,
+but does not provide backup of data.
 
 We recommend using the [CESNET storage][b] for making independent copies of your data.
 
@@ -108,10 +114,11 @@ We recommend using the [CESNET storage][b] for making independent copies of your
 !!!note
     Stage files for intensive I/O calculations onto the SCRATCH storage.
 
-The PROJECT storage is not primarily intended for computing and it is strongly recommended to avoid use of PROJECT storage directly for computing in majority of cases.
+The PROJECT storage is not primarily intended for computing and it is strongly recommended to avoid using it directly for computing in majority of cases.
 
-On the other hand, PROJECT storage is accessible from compute nodes and can be used for computing jobs with low I/O demands, when copying data to other storage for computing is not feasible or efficient .
-However, be aware of overloading the storage, as this will result in degraded performance for other users of the PROJECT storage or can cause unavailability of the PROJECT storage.
+On the other hand, the PROJECT storage is accessible from compute nodes and can be used for computing jobs with low I/O demands,
+when copying data to other storage for computing is not feasible or efficient.
+However, be aware of overloading the storage, as this will result in degraded performance for other users of the PROJECT storage or its unavailability.
 
 For maximum performance, you should always copy the files of I/O intensive jobs onto the SCRATCH storage.
 

[Jan Siwiec]

related to #78