From owner-freebsd-doc  Sun Mar 23 13:59:52 2003
Delivered-To: freebsd-doc@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 3DDA837B401; Sun, 23 Mar 2003 13:59:48 -0800 (PST)
Received: from www.reppep.com (www.reppep.com [66.92.104.200])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 1059143FBF; Sun, 23 Mar 2003 13:59:43 -0800 (PST)
	(envelope-from pepper@reppep.com)
Received: from [66.92.104.201] (g4.reppep.com [66.92.104.201])
	by www.reppep.com (Postfix) with ESMTP
	id 787C2FDC1; Sun, 23 Mar 2003 16:59:44 -0500 (EST)
Mime-Version: 1.0
X-Sender: pepper@mail.reppep.com
Message-Id: <p06000b0fbaa3c865b29c@[66.92.104.201]>
In-Reply-To: <20030323153609.GA78623@gothmog.gr>
References: <20030323.192437.59665844.hrs@eos.ocn.ne.jp>
 <p06000b08baa35a2bdcf8@[66.92.104.201]>
 <20030323153609.GA78623@gothmog.gr>
Date: Sun, 23 Mar 2003 16:58:44 -0500
To: Giorgos Keramidas <keramida@FreeBSD.org>
From: Chris Pepper <pepper@reppep.com>
Subject: Re: www/en/news/status spelling fix patch
Cc: Hiroki Sato <hrs@eos.ocn.ne.jp>, doc@FreeBSD.org
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-doc@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-doc.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-doc>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-doc>
X-Loop: FreeBSD.org

	Found a couple more still in Giorgios' patch. My changes since what Giorgios committed are marked with ->.


						Chris Pepper

>Index: report-may-2002-june-2002.xml



>@@ -82,13 +84,13 @@
>  than 256 bytes) (A full Internet view of 110k routes takes 33 MByte
>  of KVM). Another problem are pointers from and to everywhere
>  in the routing table. This makes replacing the table very hard and
>- also significantly highers the table maintainance burden (for example
>- for some kinds of updates the entire PCB has be searched lineary).
>+ also significantly highers the table maintenance burden (for example
-> also significantly raises the table maintenance burden (for example,
>+ for some kinds of updates the entire PCB has to be searched linearly).
-> for some kinds of updates the entire PCB has to be searched linearly).
> Also this is a heavy burden for SMP locking. The rewrite focuses on
>- untangeling the pointer mess, making the routing table replaceable
>+ untangling the pointer mess, making the routing table replaceable
>  and providing a more IP optimized table (5 MByte for 110k routes).
>- Other new options include policy routing and some structual alignments
>- in the network stack for clarity, cleaness and flexibilty.</p>
>+ Other new options include policy routing and some structural alignments
>+ in the network stack for clarity, cleanness and flexibility.</p>

	cleanness isn't a real word, and cleanliness isn't right either -- 'simplicity' would be good.

>  <p>The rewritten IP routing table will be ready for committing in
>  October.</p>
> </body>
>@@ -123,10 +125,10 @@
>  user structure in Switzerland. The nice thing about Switzerland
>  is that is has a very good mix of Modem/ISDN, leased line, Cable,
>  ADSL and 3G/GSM/GPRS users. Every Internet access technology is
>- represented. The goal is to analyse the behaviour of all TCP
>- sessions to the monitored sites. Parameters to be analysed include
>+ represented. The goal is to analyze the behavior of all TCP
>+ sessions to the monitored sites. Parameters to be analyzed include
>  TCP session RTT, RTT variance, in/outbound BDP, MSS changes, flow
>- control behaviour, packet loss, packet loss, packet retransmit and
>+ control behavior, packet loss, packet loss, packet retransmit and

	packet loss is repeated

>  timing of HTTP traffic to find optimal TCP parameter caching
-> timing of HTTP traffic; to find an optimal TCP parameter caching


> method.</p>
>  <p>If you have any other metrics you think is useful please contact


>@@ -975,7 +977,7 @@
>        with rtld, libc and our toolchain have been fixed. There is one remaining
>        deadlock in the web-browser code of OO.org. If anybody like to help
>        us with fixing this bug (may be another libc_r bug as it looks like)
>-       just mail me ! Unfortunalty gcc2 support got broken again with the import
>+       just mail me! Unfortunately gcc2 support got broken again with the import
>        of gcc2.95.4 in STABLE. Exceptions support seems to be broken again, we get
->       of gcc2.95.4 in STABLE. Exceptions support seems to be broken again; we get
>        internal compiler errors with c++ exceptions code. You'll have to use gcc31
>        again.</p>
>@@ -1050,7 +1052,7 @@
>   <body>
>     <p>
>        A lot of remaining PR's and Bugs have been closed. All relevant rpc
>-       concerning patches have been comitted. Thank goes to Alfred and Ian Dowese.
>+       concerning patches have been committed. Thank goes to Alfred and Ian Dowse.
->       concerning patches have been committed. Thanks go to Alfred and Ian Dowse.
>     </p>
>     <p>Jean-Luc Richier &lt;Jean-Luc.Richier@imag.fr&gt; has made a patch
>        available which adds IPv6 support to all remaining rpc servers.

>@@ -1216,7 +1218,7 @@
>   resources for the project's future evolution.  Maybe the bandwidth
>   problem can be resolved (several bandwidth offering are received!),
->  problem can be resolved (several bandwidths offers were received!),
>   but there is no answer about CPU problem (I have a plan to upgrade
->  but there is no answer about CPU problems (I have a plan to upgrade
>-  our PCs from P3-500Mhz to P4 or something better than previous).
>+  our PCs from P3-500MHz to P4 or something better than previous).
->  our PCs from P3-500MHz to P4 or better).
>   If you have interested to donate PCs to the project, please email me
->  If you are interested un donating PCs to the project, please email me
>   for more detail.
>   </p>
>Index: report-nov-2002-dec-2002.xml

>@@ -482,7 +484,7 @@
>       S&#233;bastien is still maintaining the Release Notes.</p>
> 
>     <p>We launched a new site, www.FreeBSD-fr.info, consisting in a French
->    <p>We launched a new site, www.FreeBSD-fr.info, similar to Daemon News
>-      Dameon News like site.  Netasq have donated our new server; we will
>+      Daemon News like site.  Netasq have donated our new server; we will
->      but in French.  Netasq have donated our new server; we will
>       install it in a new hosting provider in the few next weeks.  One of the
->      install it at a new hosting provider in the few next weeks.  One of the
>       big job now, project now, is the translation of the FAQ, and the big
->      big jobs now is the translation of the FAQ, and the big
>       project will be the manual pages</p>
->      project will be the manual pages.</p>


>Index: report-november-2001.xml

>@@ -732,7 +732,7 @@
>       <p>Although not strictly ATA, Promise has equipped me with a
>       couple SuperTrak sx6000 RAID controllers, they take 6 ATA disks
->      couple SuperTrak sx6000 RAID controllers; they take 6 ATA disks
>       and does RAID0-5 in hardware. I have done a driver (its an I2O
->      and do RAID0-5 in hardware. I have produced a driver (it's an I2O
>-      device) for both -current and -stable and it works butifully with
>+      device) for both -current and -stable and it works beautifully with
>       hotswap the works. It will enter the tree when it is more mature,
->      hotswap, the works. It will enter the tree when it is more mature,
>       and I have an agreement with Promise on how we handle userland
>       control util etc. BTW it seems it can also be used as a normal 6
->      control utils, etc. BTW, it seems it can also be used as a normal 6


>Index: report-sept-2002-oct-2002.xml

>@@ -267,7 +269,7 @@
>     very strong encryption of a GEOM "disk".  The algorithm has passed
>     informal review by a couple of seasoned crypto heavy-weights.
>     Any GEOM device can be protected with GBDE, entire physical disks,
>-    MBR slices, BSD paritions etc etc.  Booting from an encrypted
>+    MBR slices, BSD partitions etc etc.  Booting from an encrypted
->    MBR slices, BSD partitions, etc. etc.  Booting from an encrypted
>     partition is not possible however.</p>
->    partition is not possible, however.</p>
> 
>     <p>The focus of GBDE is to protect a "cold" disk media.  (FreeBSD is

>@@ -972,12 +974,12 @@
> 
>   <body>
>     <p>Universally Unique Identifiers (UUIDs) are 128 bit values that may
>-    be generated independently on seperate nodes (hosts), which, result in
>+    be generated independently on separate nodes (hosts), which, result in
->    be generated independently on separate nodes (hosts), which result in
>     globally unique strings.  UUIDs are also known as Globally Unique
>     Identifiers (GUIDs).  The UUID support for FreeBSD (libc) conforms to the
>     DCE 1.1 RPC specification.</p>
> 
>-    <p>UUID suport has been added to FreeBSD -CURRENT, and will be available
>+    <p>UUID support has been added to FreeBSD -CURRENT, and will be available
>     in version 5.0.  It is being extensively used in GPT partition handling
>     for IA-64 platform.  For now, a simple manual page has been provided,
>     which outlines information about the provided uuid routines.  Many


>Index: report-september-2001.xml

>@@ -689,7 +691,7 @@
>       system it should behave the same as now (and be as
>       reliable)).</p>
> 
>-      <p>Criterea for knowing when we have reached Milestione 3 is the
>+      <p>Criteria for knowing when we have reached Milestone 3 is the
>       ability for a simple process on an unloaded system to perform a
>       series of blocking syscalls reliably. e.g. open 2 sockets, and
>       send data on one, after having done a read on another,and then
->      send data on one, after having done a read on another, and then

-- 
Chris Pepper:               <http://www.reppep.com/~pepper/>
Rockefeller University:     <http://www.rockefeller.edu/>

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message