diff --git a/en/projects/netperf/cluster.sgml b/en/projects/netperf/cluster.sgml index 97b4ceef4b..deb11bc02e 100644 --- a/en/projects/netperf/cluster.sgml +++ b/en/projects/netperf/cluster.sgml @@ -1,6 +1,6 @@ - + %includes; @@ -147,12 +147,12 @@ understanding and consistent following of its procedures is important. In particular, following of the procedures makes it easier for developers to have reasonable expectations about the configuration of - systems in the cluster, as well as to avoid trading on each others + systems in the cluster, as well as to avoid treading on each others toes.
Reserving a system is currently done on an ad hoc basis. - A wikki used to system reservation will shortly be introduced. In + A wiki used to system reservation will shortly be introduced. In general, it is recommended that reservations of systems occur for periods of 8 hours or shorter, in order to facilitate shared use, although longer tests or experiments are certainly possible.
Currently, no automated reservation system is in place for the netperf cluster, but we hope to introduce some system for reservation shortly. - In the mean time, the following standing reservations are in palce for + In the meantime, the following standing reservations are in place for the netperf cluster: