diff --git a/docs.it4i/anselm/prace.md b/docs.it4i/anselm/prace.md
index 061cd0a0714075f3caca51152363e10ff795176f..28980cc7322649993089744ae6ba6caa13912d53 100644
--- a/docs.it4i/anselm/prace.md
+++ b/docs.it4i/anselm/prace.md
@@ -2,15 +2,15 @@
## Intro
-PRACE users coming to Anselm as to TIER-1 system offered through the DECI calls are in general treated as standard users and so most of the general documentation applies to them as well. This section shows the main differences for quicker orientation, but often uses references to the original documentation. PRACE users who don't undergo the full procedure (including signing the IT4I AuP on top of the PRACE AuP) will not have a password and thus access to some services intended for regular users. This can lower their comfort, but otherwise they should be able to use the TIER-1 system as intended. Please see the [Obtaining Login Credentials section](../general/obtaining-login-credentials/obtaining-login-credentials/), if the same level of access is required.
+PRACE users coming to Anselm as to TIER-1 system offered through the DECI calls are in general treated as standard users and so most of the general documentation applies to them as well. This section shows the main differences for quicker orientation, but often uses references to the original documentation. PRACE users who don't undergo the full procedure (including signing the IT4I AuP on top of the PRACE AuP) will not have a password and thus access to some services intended for regular users. This is inconvenient, but otherwise they should be able to use the TIER-1 system as intended. Please see the [Obtaining Login Credentials section](../general/obtaining-login-credentials/obtaining-login-credentials/), if the same level of access is required.
-All general [PRACE User Documentation](http://www.prace-ri.eu/user-documentation/) should be read before continuing reading the local documentation here.
+All general [PRACE User Documentation](http://www.prace-ri.eu/user-documentation/) should be read before continuing to read the local documentation here.
## Help and Support
-If you have any troubles, need information, request support or want to install additional software, please use [PRACE Helpdesk](http://www.prace-ri.eu/helpdesk-guide264/).
+If you have any troubles, need information, require support or want to install additional software, please use the [PRACE Helpdesk](http://www.prace-ri.eu/helpdesk-guide264/).
-Information about the local services are provided in the [introduction of general user documentation](introduction/). Please keep in mind, that standard PRACE accounts don't have a password to access the web interface of the local (IT4Innovations) request tracker and thus a new ticket should be created by sending an e-mail to support[at]it4i.cz.
+Information about the local services is provided in the [introduction of the general user documentation](introduction/). Please keep in mind, that standard PRACE accounts don't have a password to access the web interface of the local (IT4Innovations) request tracker and thus a new ticket should be created by sending an e-mail to support[at]it4i.cz.
## Obtaining Login Credentials
@@ -22,7 +22,7 @@ If there's a special need a PRACE user can get a standard (local) account at IT4
### Access With GSI-SSH
-For all PRACE users the method for interactive access (login) and data transfer based on grid services from Globus Toolkit (GSI SSH and GridFTP) is supported.
+For all PRACE users, the method for interactive access (login) and data transfer based on grid services from the Globus Toolkit (GSI SSH and GridFTP) is supported.
The user will need a valid certificate and to be present in the PRACE LDAP (please contact your HOME SITE or the primary investigator of your project for LDAP account creation).
@@ -40,17 +40,17 @@ Before you start to use any of the services don't forget to create a proxy certi
$ grid-proxy-init
```
-To check whether your proxy certificate is still valid (by default it's valid 12 hours), use:
+To check whether your proxy certificate is still valid (by default it's valid for 12 hours), use:
```console
$ grid-proxy-info
```
-To access Anselm cluster, two login nodes running GSI SSH service are available. The service is available from public Internet as well as from the internal PRACE network (accessible only from other PRACE partners).
+To access the Anselm cluster, two login nodes running GSI SSH service are available. The service is available publicly on the Internet as well as on the internal PRACE network (only accessible to other PRACE partners).
-#### Access From PRACE Network:
+#### Access From the PRACE Network:
-It is recommended to use the single DNS name anselm-prace.it4i.cz which is distributed between the two login nodes. If needed, user can login directly to one of the login nodes. The addresses are:
+It is recommended to use the single DNS name anselm-prace.it4i.cz which is distributed between the two login nodes. If needed, the user can login directly to one of the login nodes. The addresses are:
| Login address | Port | Protocol | Login node |
| --------------------------- | ---- | -------- | ---------------- |
@@ -62,15 +62,15 @@ It is recommended to use the single DNS name anselm-prace.it4i.cz which is distr
$ gsissh -p 2222 anselm-prace.it4i.cz
```
-When logging from other PRACE system, the prace_service script can be used:
+When logging in from another PRACE system, the prace_service script can be used:
```console
$ gsissh `prace_service -i -s anselm`
```
-#### Access From Public Internet:
+#### Public Access From the Internet:
-It is recommended to use the single DNS name anselm.it4i.cz which is distributed between the two login nodes. If needed, user can login directly to one of the login nodes. The addresses are:
+It is recommended to use the single DNS name anselm.it4i.cz which is distributed between the two login nodes. If needed, the user can login directly to one of the login nodes. The addresses are:
| Login address | Port | Protocol | Login node |
| --------------------- | ---- | -------- | ---------------- |
@@ -82,13 +82,13 @@ It is recommended to use the single DNS name anselm.it4i.cz which is distributed
$ gsissh -p 2222 anselm.it4i.cz
```
-When logging from other PRACE system, the prace_service script can be used:
+When logging in from another PRACE system, the prace_service script can be used:
```console
$ gsissh `prace_service -e -s anselm`
```
-Although the preferred and recommended file transfer mechanism is [using GridFTP](prace/#file-transfers), the GSI SSH implementation on Anselm supports also SCP, so for small files transfer gsiscp can be used:
+Although the preferred and recommended file transfer mechanism is [using GridFTP](prace/#file-transfers), the GSI SSH implementation on Anselm also supports SCP, so for small files transfer gsiscp can be used:
```console
$ gsiscp -P 2222 _LOCAL_PATH_TO_YOUR_FILE_ anselm.it4i.cz:_ANSELM_PATH_TO_YOUR_FILE_
@@ -102,7 +102,7 @@ $ gsiscp -P 2222 anselm-prace.it4i.cz:_ANSELM_PATH_TO_YOUR_FILE_ _LOCAL_PATH_TO_
### Access to X11 Applications (VNC)
-If the user needs to run X11 based graphical application and does not have a X11 server, the applications can be run using VNC service. If the user is using regular SSH based access, please see the section in general documentation.
+If the user needs to run an X11 based graphical application and does not have an X11 server, the applications can be run using a VNC service. If the user is using regular SSH based access, please see the relevant section in general documentation.
If the user uses GSI SSH based access, then the procedure is similar to the SSH based access, only the port forwarding must be done using GSI SSH:
@@ -112,17 +112,17 @@ $ gsissh -p 2222 anselm.it4i.cz -L 5961:localhost:5961
### Access With SSH
-After successful obtainment of login credentials for the local IT4Innovations account, the PRACE users can access the cluster as regular users using SSH. For more information please see the section in general documentation.
+After successful obtainment of login credentials for the local IT4Innovations account, PRACE users can access the cluster as regular users using SSH. For more information please see the section in general documentation.
## File Transfers
-PRACE users can use the same transfer mechanisms as regular users (if they've undergone the full registration procedure). For information about this, please see the section in the general documentation.
+PRACE users can use the same transfer mechanisms as regular users (if they've undergone the full registration procedure). For information about this, please see the relevant section in the general documentation.
-Apart from the standard mechanisms, for PRACE users to transfer data to/from Anselm cluster, a GridFTP server running Globus Toolkit GridFTP service is available. The service is available from public Internet as well as from the internal PRACE network (accessible only from other PRACE partners).
+Apart from the standard mechanisms, for PRACE users to transfer data to/from the Anselm cluster, a GridFTP server running the Globus Toolkit GridFTP service is available. The service is available publicly over the Internet as well as from the internal PRACE network (accessible only to other PRACE partners).
-There's one control server and three backend servers for striping and/or backup in case one of them would fail.
+There is one control server and three backend servers for striping and/or backup in case any of them were to fail.
-### Access From PRACE Network
+### Access From the PRACE Network
| Login address | Port | Node role |
| ---------------------------- | ---- | --------------------------- |
@@ -137,25 +137,25 @@ Copy files **to** Anselm by running the following commands on your local machine
$ globus-url-copy file://_LOCAL_PATH_TO_YOUR_FILE_ gsiftp://gridftp-prace.anselm.it4i.cz:2812/home/prace/_YOUR_ACCOUNT_ON_ANSELM_/_PATH_TO_YOUR_FILE_
```
-Or by using prace_service script:
+Or by using the prace_service script:
```console
$ globus-url-copy file://_LOCAL_PATH_TO_YOUR_FILE_ gsiftp://`prace_service -i -f anselm`/home/prace/_YOUR_ACCOUNT_ON_ANSELM_/_PATH_TO_YOUR_FILE_
```
-Copy files **from** Anselm:
+Copy files **from** Anselm with:
```console
$ globus-url-copy gsiftp://gridftp-prace.anselm.it4i.cz:2812/home/prace/_YOUR_ACCOUNT_ON_ANSELM_/_PATH_TO_YOUR_FILE_ file://_LOCAL_PATH_TO_YOUR_FILE_
```
-Or by using prace_service script:
+Or by using the prace_service script:
```console
$ globus-url-copy gsiftp://`prace_service -i -f anselm`/home/prace/_YOUR_ACCOUNT_ON_ANSELM_/_PATH_TO_YOUR_FILE_ file://_LOCAL_PATH_TO_YOUR_FILE_
```
-### Access From Public Internet
+### Public Access From the Internet
| Login address | Port | Node role |
| ---------------------- | ---- | --------------------------- |
@@ -170,19 +170,19 @@ Copy files **to** Anselm by running the following commands on your local machine
$ globus-url-copy file://_LOCAL_PATH_TO_YOUR_FILE_ gsiftp://gridftp.anselm.it4i.cz:2812/home/prace/_YOUR_ACCOUNT_ON_ANSELM_/_PATH_TO_YOUR_FILE_
```
-Or by using prace_service script:
+Or by using the prace_service script:
```console
$ globus-url-copy file://_LOCAL_PATH_TO_YOUR_FILE_ gsiftp://`prace_service -e -f anselm`/home/prace/_YOUR_ACCOUNT_ON_ANSELM_/_PATH_TO_YOUR_FILE_
```
-Copy files **from** Anselm:
+Copy files **from** Anselm with:
```console
$ globus-url-copy gsiftp://gridftp.anselm.it4i.cz:2812/home/prace/_YOUR_ACCOUNT_ON_ANSELM_/_PATH_TO_YOUR_FILE_ file://_LOCAL_PATH_TO_YOUR_FILE_
```
-Or by using prace_service script:
+Or by using the prace_service script:
```console
$ globus-url-copy gsiftp://`prace_service -e -f anselm`/home/prace/_YOUR_ACCOUNT_ON_ANSELM_/_PATH_TO_YOUR_FILE_ file://_LOCAL_PATH_TO_YOUR_FILE_
@@ -199,15 +199,15 @@ More information about the shared file systems is available [here](storage/).
## Usage of the Cluster
-There are some limitations for PRACE user when using the cluster. By default PRACE users aren't allowed to access special queues in the PBS Pro to have high priority or exclusive access to some special equipment like accelerated nodes and high memory (fat) nodes. There may be also restrictions obtaining a working license for the commercial software installed on the cluster, mostly because of the license agreement or because of insufficient amount of licenses.
+There are some limitations for PRACE users when using the cluster. By default PRACE users aren't allowed to access special queues in the PBS Pro to have high priority or exclusive access to some special equipment like accelerated nodes and high memory (fat) nodes. There may also be restrictions when obtaining a working license for the commercial software installed on the cluster, mostly because of the license agreement or because of insufficient amounts of licenses.
-For production runs always use scratch file systems, either the global shared or the local ones. The available file systems are described [here](hardware-overview/).
+For production runs always use the scratch file systems, either the global shared or the local ones. The available file systems are described [here](hardware-overview/).
-### Software, Modules and PRACE Common Production Environment
+### Software, Modules, and the PRACE Common Production Environment
-All system wide installed software on the cluster is made available to the users via the modules. The information about the environment and modules usage is in this [section of general documentation](environment-and-modules/).
+All system wide installed software on the cluster is made available to users via the modules. The information about environment and module usage is in this [section of general documentation](environment-and-modules/).
-PRACE users can use the "prace" module to use the [PRACE Common Production Environment](http://www.prace-ri.eu/prace-common-production-environment/).
+PRACE users, via the "prace" module, can use the [PRACE Common Production Environment](http://www.prace-ri.eu/prace-common-production-environment/);
```console
$ module load prace
@@ -225,15 +225,15 @@ For PRACE users, the default production run queue is "qprace". PRACE users can a
| **qprace** Production queue | yes | > 0 | 178 w/o accelerator | medium | no | 24 / 48 h |
| **qfree** Free resource queue | yes | none required | 178 w/o accelerator | very low | no | 12 / 12 h |
-**qprace**, the PRACE: This queue is intended for normal production runs. It is required that active project with nonzero remaining resources is specified to enter the qprace. The queue runs with medium priority and no special authorization is required to use it. The maximum runtime in qprace is 12 hours. If the job needs longer time, it must use checkpoint/restart functionality.
+**qprace**, the PRACE queue: This queue is intended for normal production runs. It is required that an active project with nonzero remaining resources is specified to enter the qprace. The queue runs with medium priority and no special authorization is required to use it. The maximum runtime in qprace is 12 hours. If the job needs a longer time, it must use checkpoint/restart functionality.
### Accounting & Quota
-The resources that are currently subject to accounting are the core hours. The core hours are accounted on the wall clock basis. The accounting runs whenever the computational cores are allocated or blocked via the PBS Pro workload manager (the qsub command), regardless of whether the cores are actually used for any calculation. See [example in the general documentation](resources-allocation-policy/).
+The resources that are currently subject to accounting are the core hours. The core hours are accounted on the basis of wall clock time. The accounting runs whenever the computational cores are allocated or blocked via the PBS Pro workload manager (the qsub command), regardless of whether the cores are actually used for any calculation. See the [example in the general documentation](resources-allocation-policy/).
PRACE users should check their project accounting using the [PRACE Accounting Tool (DART)](http://www.prace-ri.eu/accounting-report-tool/).
-Users who have undergone the full local registration procedure (including signing the IT4Innovations Acceptable Use Policy) and who have received local password may check at any time, how many core-hours have been consumed by themselves and their projects using the command "it4ifree".
+Users who have undergone the full local registration procedure (including signing the IT4Innovations Acceptable Use Policy) and who have received a local password may check at any time, how many core-hours have been consumed by themselves and their projects using the command "it4ifree".
!!! note
You need to know your user password to use the command. Displayed core hours are "system core hours" which differ from PRACE "standardized core hours".
@@ -250,7 +250,7 @@ $ it4ifree
DD-13-1 10000 2606 2606 7394
```
-By default file system quota is applied. To check the current status of the quota use
+By default a file system quota is applied. To check the current status of the quota use;
```console
$ lfs quota -u USER_LOGIN /home