Proofread

docs.it4i/salomon/resources-allocation-policy.md

@@ -33,9 +33,9 @@ The resources are allocated to the job in a fair-share fashion, subject to const
 
 ### Queue notes
 
-The job wall clock time defaults to **half the maximum time**, see table above. Longer wall time limits can be  [set manually, see examples](job-submission-and-execution/).
+The job wall-clock time defaults to **half the maximum time**, see table above. Longer wall time limits can be  [set manually, see examples](job-submission-and-execution/).
 
-Jobs that exceed the reserved wall clock time (Req'd Time) get killed automatically. Wall clock time limit can be changed for queuing jobs (state Q) using the qalter command, however can not be changed for a running job (state R).
+Jobs that exceed the reserved wall-clock time (Req'd Time) get killed automatically. Wall-clock time limit can be changed for queuing jobs (state Q) using the qalter command, however can not be changed for a running job (state R).
 
 Salomon users may check current queue configuration at <https://extranet.it4i.cz/rsweb/salomon/queues>.
 
@@ -116,7 +116,7 @@ Options:
 ### Wall-clock Core-Hours WCH
 
 The wall-clock core-hours (WCH) are the basic metric of computer utilization time.
-1 wall-clock core-hour is defined as 1 processor core allocated for 1 hour of wall clock time. Allocating a full node (24 cores)
+1 wall-clock core-hour is defined as 1 processor core allocated for 1 hour of wall-clock time. Allocating a full node (24 cores)
 for 1 hour amounts to 24 wall-clock core-hours.
 
 ### Standard Core-Hours SCH
@@ -127,27 +127,27 @@ The standard core-hours are obtained from WCH by applying a standardization fact
 ---8<--- "sch_formula.md"
 
 The accounting runs whenever the computational cores are allocated via the PBS Pro workload manager (the qsub command), regardless of whether
-the cores are actually used for any calculation. All jobs are accounted in standard core hours, using factor F valid at the time of the execution:
+the cores are actually used for any calculation. All jobs are accounted in standard core-hours, using factor F valid at the time of the execution:
 
-| System                          | F   | validity |
+| System                          | F   | Validity |
 | ------------------------------- | -   | -------- |
-| Salomon                         | 1.00 |  2017-09-05 to 2018-06-01 |
-| Anselm                          | 0.65 |  2017-09-05 to 2018-06-01 |
+| Salomon                         | 1.00 |  2017-09-11 to 2018-06-01 |
+| Anselm                          | 0.65 |  2017-09-11 to 2018-06-01 |
 
 !!! note
     The allocations are requested/granted in standard core-hours SCH.
 
 Whenever the term core-hour is used in this documentation, we mean the standard core-hour, SCH.
 
-The standard core hours were introduced to treat systems of different age on equal footing.
-Standard core hour is an accounting tool to discount the legacy systems. The past (before 2017=09-05) F factors are all 1.0.
+The standard core-hours were introduced to treat systems of different age on equal footing.
+Standard core-hour is an accounting tool to discount the legacy systems. The past (before 2017-09-05) F factors are all 1.0.
 In future, the factors F will be updated, as new systems are installed. Factors F are expected to only decrease in time.
 
 See examples in the [Job submission and execution](job-submission-and-execution/) section.
 
 ### Consumed Resources
 
-User may check at any time, how many core-hours have been consumed by himself/herself and his/her projects. The command is available on clusters' login nodes.
+User may check at any time, how many core-hours have been consumed by himself/herself and his/her projects. The command is available on cluster login nodes.
 
 ```console
 $ it4ifree