--- site/data/main/Attic/index.cgi	2004/07/12 18:34:12	1.9
+++ site/data/main/Attic/index.cgi	2004/07/12 19:53:16	1.10
@@ -3,22 +3,19 @@
 # $DragonFly$
 
 $TITLE(The DragonFly BSD Project)
-<h1>NEWS!</h1>
-<p>
-12-Jul-2004: DragonFly's first release, 1.0, is here!  Visit the download page for a
-list of download links for the ISO!
-</p>
-<ul>
+<table border="0" width="100%" bgcolor="white">
+<tr><td align="center">
     <h1>DragonFly-1.0 RELEASED!</h1>
-    <h1>http://www.dragonflybsd.org/</h1>
     <h1>12 July 2004</h1>
+</td></tr></table>
 
     <p>
 One year after starting the project as a fork off the FreeBSD-4.x tree,
-the DragonFly team is pleased to announce our 1.0 release!</p>
+the <a href="http://www.dragonflybsd.org/main/team.cgi">DragonFly Team</a>
+is pleased to announce our 1.0 release!</p>
 
     <p>
-We've made excellent progress in our first year.  We have replaced nearly
+We've made remarkable progress in our first year.  We have replaced nearly
 all of the core threading, process, interrupt, and network infrastructure 
 with DragonFly native subsystems.  We have our own MP-friendly slab allocator,
 a Light Weight Kernel Threading (LWKT) system that is separate from the
@@ -38,15 +35,16 @@ as the original 4.x UP-centric code is o
 We have made excellent progress bringing in those pieces from FreeBSD, NetBSD,
 and OpenBSD that fit our model.  For example, NEWBUS/BUS_DMA, the USB 
 infrastructure, RCNG (next generation system startup infrastructure), and
-so forth, and we have made an excellent start reformulating the build
+so forth.  We have made an excellent start on reformulating the build
 and release infrastructure including an excellent new system installer
 which, while still in its infancy for the 1.0 release, has been coded in
 a manner that will allow us to greatly improve and expand its capabilities
 in coming months.</p>
 
     <p>
-We have done so much that it cannot all be listed here.  Please checkout the
-diary on our main site for the technical minutia.</p>
+We have done so much that it cannot all be listed here.  Please check out the
+<a href="http://www.dragonflybsd.org/status/diary.cgi">Diary</a> for
+technical details.</p>
 
     <p>
 The two largest user-visible subsystems that still have major work pending
@@ -59,13 +57,10 @@ forefront of the work for the next year,
 removing the BGL (Big Giant Lock, also known as the MP lock) from code
 inherited from 4.x, threading the VFS (Virtual File System) subsystem (the
 network subsystem is already threaded as of 1.0), and implementing
-asynchronous messaged system calls.  And that is just the tip of the iceberg,
-we will be doing far more in the coming year!</p>
+asynchronously messaged system calls.  And that is just the tip of the iceberg,
+for we will be achieving far more in the coming year!</p>
 
-    <br />
-					-The DragonFly Team-
-</ul>
-<h1>What is it?</h1>
+<h1>What is DragonFly BSD?</h1>
 <p>
 DragonFly is an operating system and environment designed to be the logical
 continuation of the FreeBSD-4.x OS series.  These operating systems belong