os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Fix typos.

Browse source
This commit is contained in:
Christian Brueffer 2005-01-31 14:05:53 +00:00
parent 4a794536a0
commit 87d64840f9
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=23702
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
en/projects/netperf/cluster.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/projects/netperf/cluster.sgml,v 1.1 2005/01/31 12:07:56 rwatson Exp $">
<!ENTITY date "$FreeBSD: www/en/projects/netperf/cluster.sgml,v 1.2 2005/01/31 12:12:56 rwatson Exp $">
<!ENTITY title "FreeBSD Network Performance Project (netperf)">
<!ENTITY email 'mux'>
<!ENTITY % includes SYSTEM "../../includes.sgml"> %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.</p>
<ul>
<li><p><b>Reserving a system</b> 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.</p></li>
@ -218,7 +218,7 @@
<p>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:</p>
<table border=1>