diff --git a/en/releases/4.10R/todo.sgml b/en/releases/4.10R/todo.sgml
index 31d6ee0b30..ae9e1e728d 100644
--- a/en/releases/4.10R/todo.sgml
+++ b/en/releases/4.10R/todo.sgml
@@ -1,104 +1,105 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
 <!ENTITY base CDATA "../..">
 <!ENTITY email 'freebsd-qa'>
-<!ENTITY date "$FreeBSD: www/en/releases/4.10R/todo.sgml,v 1.2 2004/05/05 21:37:41 hrs Exp $">
+<!ENTITY date "$FreeBSD: www/en/releases/4.10R/todo.sgml,v 1.3 2004/05/12 15:41:35 hrs Exp $">
 <!ENTITY local.rel "4.10">
 <!ENTITY title "FreeBSD &local.rel; Open Issues">
 <!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
 <!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
 <!ENTITY status.na "<font color=green>N/A</font>">
 <!ENTITY status.done "<font color=green>Done</font>">
 <!ENTITY status.wip "<font color=blue>In&nbsp;progress</font>">
 <!ENTITY status.untested "<font color=orange>Needs&nbsp;testing</font>">
 <!ENTITY status.new "<font color=red>Not&nbsp;done</font>">
 <!ENTITY status.unknown "<font color=red>Unknown</font>">
 ]>
 
 <html>
 &header;
 
 <h1>Open Issues</h1>
 
 <p>This is a list of open issues that need to be resolved for FreeBSD
   &local.rel;.  If you have any updates for this list, please e-mail
   re@FreeBSD.org.</p>
 
 <p>As many of these open issues involve merging bus_dma driver changes
   from -CURRENT, the <a
   href="&base;/projects/busdma/index.html">busdma</a> project page is
   also useful.</p>
 
 <h3>Must Resolve Issues for &local.rel;-RC3</h3>
 
 <table border=1 width="100%">
   <tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
       </tr>
 
 </table>
 
 
 <h3>Must Resolve Issues for &local.rel;-RELEASE</h3>
 
 <table border=1 width="100%">
   <tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
       </tr>
 
 </table>
 
 <h3>Desired Features for &local.rel;-RELEASE</h3>
 
 <table border=1 width="100%">
   <tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
       </tr>
 </table>
 
 <h3>Documentation items that must be resolved for &local.rel;</h3>
 
 <table border=1 width="100%">
   <tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
       </tr>
 
 </table>
 
 <h3>Testing focuses for &local.rel;</h3>
 
 <table border=1 width="100%">
   <tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
       </tr>
 
 	<tr>
 	  <td>twe(4) stability problem</td>
 	  <td>&status.untested;</td>
 	  <td>--</td>
 	  <td>The twe(4) driver has a stability problem
 	    when a lot of rapid sequential small file
 	    inserts into a new directory tree.  A set of patches
 	    for the problem has been committed just before 4.10-RC3.</td>
 	</tr>
 
 	<tr>
 	  <td>vmspace leak</td>
 	  <td>&status.untested;</td>
 	  <td>--</td>
 	  <td>Copying vm_exitingcnt to the new vmspace in vmspace_exec()
 	    can make it very high values and never drop to 0 and
 	    be freed.  This can cause a system crash.  A patch for the
 	    problem has been committed just before 4.10-RC3.</td>
 	</tr>
 
 	<tr>
 	  <td>twa(4) fails in sysinstall</td>
-	  <td>&status.wip;</td>
+	  <td>&status.untested;</td>
 	  <td>--</td>
 	  <td>When a twa(4) device in a system with no SCSI controller
 	    is detected, sysinstall in 4.10-RC2 does not recognize
 	    the disks attached.  It seems that
 	    this problem may involve inconsistency between the CAM
-	    device rescanning and the kernel module loading.</td>
+	    device rescanning and the kernel module loading.
+	    A patch for the problem has been committed just before 4.10-RC3.</td>
 	</tr>
 </table>
 
     &footer;
 
   </body>
 </html>

Issue	Status	Responsible	Description
twe(4) stability problem	&status.untested;	--	The twe(4) driver has a stability problem when a lot of rapid sequential small file inserts into a new directory tree. A set of patches for the problem has been committed just before 4.10-RC3.
vmspace leak	&status.untested;	--	Copying vm_exitingcnt to the new vmspace in vmspace_exec() can make it very high values and never drop to 0 and be freed. This can cause a system crash. A patch for the problem has been committed just before 4.10-RC3.
twa(4) fails in sysinstall	&status.wip;	&status.untested;	--	When a twa(4) device in a system with no SCSI controller is detected, sysinstall in 4.10-RC2 does not recognize the disks attached. It seems that this problem may involve inconsistency between the CAM - device rescanning and the kernel module loading.