diff --git a/en/releases/4.8R/schedule.sgml b/en/releases/4.8R/schedule.sgml
index a58ab0aa18..6bb26c6014 100644
--- a/en/releases/4.8R/schedule.sgml
+++ b/en/releases/4.8R/schedule.sgml
@@ -19,7 +19,7 @@
 
 <p>General discussions about the release engineering process or
   quality assurance issues should be sent to the public <a
-  href="mailto:freebsd-qa@FreeBSD.org">freebsd-qa</a> mailing list.
+  href="mailto:FreeBSD-qa@FreeBSD.org">freebsd-qa</a> mailing list.
   <a
   href="&base;/doc/en_US.ISO8859-1/books/faq/misc.html#DEFINE-MFC">MFC</a>
   requests should be sent to <a
@@ -35,7 +35,7 @@
     <td>16&nbsp;Jan&nbsp;2003</td>
     <td>16&nbsp;Jan&nbsp;2003</td>
     <td>Release Engineers send announcement email to
-      developers@FreeBSD.org with a rough schedule for the FreeBSD
+      <tt>developers@FreeBSD.org</tt> with a rough schedule for the FreeBSD
       &local.rel; release.</td>
   </tr>
   <tr>
@@ -79,7 +79,7 @@
       href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>.  Certain highly
       active documentation committers are exempt from this rule for
       routine man page / release note updates.  Heads-up emails
-      should be sent to the developers@, stable@, and qa@ lists.</td>
+      should be sent to the <tt>developers@</tt>, <tt>stable@</tt> and <tt>qa@</tt> lists.</td>
   </tr>
 
   <tr>
@@ -107,12 +107,12 @@
       <tt>ftp-master.freebsd.org</tt> and
     <tt>releng4.freebsd.org</tt>.  A network install directory should
     be uploaded to <tt>ftp-master.freebsd.org</tt>.  The
-    <tt>packages</tt> directory should be a <em>relative</em> symlink,
+    <tt>packages/</tt> directory should be a <em>relative</em> symlink,
     as described in the releng article.
   </tr>
 
   <tr>
-    <td>Heads up to -stable</td>
+    <td>Heads up to <tt>-stable</tt></td>
     <td>2 Mar 2003</td>
     <td>3 Mar 2003</td>
     <td>A message should be sent to <tt>qa@FreeBSD.org</tt> and
@@ -122,7 +122,7 @@
   <tr>
     <td>Second release candidate</td>
     <td>16 Mar 2003</td>
-    <td>--</td>
+    <td>17 Mar 2003</td>
     <td>Note: the release date of this candidate depends on the user
     experience with RC1.</td>
   </tr>
@@ -174,8 +174,8 @@
   <tr>
     <td>Ports tree unfrozen</td>
     <td>22 Mar 2003</td>
-    <td>--</td>
-    <td>After the <tt>ports</tt> tree is tagged,
+    <td>22 Mar 2003</td>
+    <td>After the <tt>ports/</tt> tree is tagged,
       the <tt>ports/</tt> tree will be re-opened for commits, but
       commits made after tagging will not go in &local.rel;-RELEASE.</td>
   </tr>
@@ -192,7 +192,7 @@
   <tr>
     <td><tt>doc/</tt> tree tagged.</td>
     <td>19 Mar 2003</td>
-    <td>--</td>
+    <td>22 Mar 2003</td>
     <td>Version number bumps for <tt>doc/</tt> subtree.
       <tt>RELEASE_4_8_0</tt> tag for <tt>doc/</tt>.  <tt>doc/</tt>
       slush ends at this time.</td>
@@ -201,7 +201,7 @@
   <tr>
     <td><tt>RELENG_4_8</tt> branch</td>
     <td>22 Mar 2003</td>
-    <td>--</td>
+    <td>23 Mar 2003</td>
     <td>The release branch is created.</td>
   </tr>
 
@@ -238,7 +238,7 @@
     <td>src tree tagged.</td>
     <td>23 Mar 2003</td>
     <td>--</td>
-    <td><tt>RELENG_4_8_0_RELEASE</tt> tag for src.</td>
+    <td><tt>RELENG_4_8_0_RELEASE</tt> tag for <tt>src/</tt>.</td>
   </tr>
 
   <tr>
@@ -278,9 +278,9 @@
     <td>Unfreeze the tree</td>
     <td>24 Mar 2003</td>
     <td>--</td>
-    <td>Announcement to developers@ explaining that the release is
-     out, and commits to RELENG_4 no longer require approval.  Also
-     note the policy for commits to the RELENG_4_8 branch.</td>
+    <td>Announcement to <tt>developers@</tt> explaining that the release is
+     out, and commits to <tt>RELENG_4</tt> no longer require approval.  Also
+     note the policy for commits to the <tt>RELENG_4_8</tt> branch.</td>
   </tr>