This page needs a substantial rewrite, but I've at least corrected

some of the stats.

Partially suggested by:	PR#9193

en_US.ISO8859-1/books/handbook/introduction/chapter.sgml

@@ -1,7 +1,7 @@
 <!--
      The FreeBSD Documentation Project
 
-     $Id: chapter.sgml,v 1.10 1999-03-08 22:04:42 nik Exp $
+     $Id: chapter.sgml,v 1.11 1999-05-07 05:25:11 jkh Exp $
 -->
 
 <chapter id="introduction">
@@ -308,12 +308,12 @@
       Berkeley's CSRG had removed large chunks of code required for actually
       constructing a bootable running system (due to various legal
       requirements) and the fact that the Intel port of 4.4 was highly
-      incomplete.  It took the project until December of 1994 to make this
-      transition, and in January of 1995 it released FreeBSD 2.0 to the net
-      and on CDROM.  Despite being still more than a little rough around the
-      edges, the release was a significant success and was followed by the
-      more robust and easier to install FreeBSD 2.0.5 release in June of
-      1995.</para>
+      incomplete.  It took the project until November of 1994 to make this
+      transition, at which point it released FreeBSD 2.0 to the net
+      and on CDROM (in late December).  Despite being still more than a little
+      rough around the edges, the release was a significant success and was
+      followed by the more robust and easier to install FreeBSD 2.0.5 release
+      in June of 1995.</para>
 	
     <para>We released FreeBSD 2.1.5 in August of 1996, and it appeared to be
       popular enough among the ISP and commercial communities that another
@@ -332,8 +332,8 @@
       the 2.2 branch, 2.2.8, appeared in November, 1998.</para>
 
     <para>The tree branched again on Jan 20, 1999.  This led to 4.0-current
-      and a 3.x-stable branch, from which 3.1 will be released on February
-      15th, 1999.</para>
+      and a 3.x-stable branch, from which 3.1 was released on February
+      15th, 1999 and 3.2 was released on May 15, 1999.</para>
 
     <para>Long term development projects will continue to take place in the
       4.0-current branch and SNAPshot releases of 4.0 on CDROM (and, of
@@ -362,7 +362,7 @@
       rather than the usual opposite.  Due to the additional complexities that
       can evolve in the commercial use of GPL software, we do, however,
       endeavor to replace such software with submissions under the more
-      relaxed BSD copyright whenever possible.</para>
+      relaxed BSD copyright when reasonable to do so.</para>
   </sect1>
   
   <sect1 id="development">
@@ -509,14 +509,14 @@
       group, with some enhancements from NetBSD, OpenBSD, 386BSD, and the Free
       Software Foundation.</para>
 	
-    <para>Since our release of FreeBSD 2.0 in January of 95, the performance,
+    <para>Since our release of FreeBSD 2.0 in late 94, the performance,
       feature set, and stability of FreeBSD has improved dramatically.  The
       largest change is a revamped virtual memory system with a merged VM/file
       buffer  cache that not only increases performance, but reduces FreeBSD's
       memory footprint, making a 5MB configuration a more acceptable minimum.
       Other enhancements include full NIS client and server support,
       transaction TCP support, dial-on-demand PPP, an improved SCSI subsystem,
-      early ISDN support, support for FDDI and Fast Ethernet (100Mbit)
+      ISDN support, support for ATM, FDDI and Fast Ethernet (100Mbit)
       adapters, improved support for the Adaptec 2940 (WIDE and narrow) and
       many hundreds of bug fixes.</para>
 	
@@ -527,10 +527,10 @@
 	
     <para>In addition to the base distributions, FreeBSD offers a new ported
       software collection with hundreds of commonly sought-after programs.  At
-      the end of August 1998 there were more than 1700 ports! The list of
+      the end of April 1999 there were more than 2300 ports! The list of
       ports ranges from http (WWW) servers, to games, languages, editors and
       almost everything in between.  The entire ports collection requires
-      approximately 26MB of storage, all ports being  expressed as
+      approximately 50MB of storage, all ports being  expressed as
       &ldquo;deltas&rdquo; to their original sources.  This makes  it much
       easier for us to update ports, and greatly reduces the disk space
       demands made by the older 1.0 ports collection.  To compile a port, you