diff --git a/en/portmgr/index.sgml b/en/portmgr/index.sgml
index bf0570e519..2efc1a57cd 100644
--- a/en/portmgr/index.sgml
+++ b/en/portmgr/index.sgml
@@ -1,114 +1,114 @@
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
 <!ENTITY base CDATA "..">
-<!ENTITY date "$FreeBSD$">
+<!ENTITY date "$FreeBSD: www/en/portmgr/index.sgml,v 1.1 2005/03/12 07:30:25 linimon Exp $">
 <!ENTITY email 'portmgr'>
 <!ENTITY title "Ports Management Team">
 <!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
 <!ENTITY % developers SYSTEM "../developers.sgml"> %developers;
 <!ENTITY contact.re '<a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>'>
 <!ENTITY contact.so '<a href="mailto:security-officer@FreeBSD.org">security-officer@FreeBSD.org</a>'>
 <!ENTITY contact.portmgr '<a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>'>
 ]>
 
 <html>
 &header;
 
 <p>The FreeBSD Ports Management Team (also known as <tt>portmgr</tt>
   due to its email alias) is responsible for issues relating to the
   <a href="http://www.FreeBSD.org/ports">FreeBSD Ports Collection</a>.</p>
 
 <h3><a href="charter.html">Charter</a></h3>
 
 <p>Discusses the goals, rights, and responsibilities of the team.
-The contents of this document are (XXX to be) approved by the FreeBSD
+The contents of this document are approved by the FreeBSD
 Core Team.</p>
 
 <h3><a href="policies.html">Policies</a></h3>
 
 <p>Discusses current policies that the team has adopted to meet
 its goals.</p>
 
 <h3><a href="qa.html">Quality Assurance Activities</a></h3>
 
 <p>A behind-the-scenes look at the efforts that are made to ensure that
   the Ports Collection works as well as it possibly can.</p>
 
 <h3>Team Members</h3>
 
 <p><a href="mailto:portmgr@FreeBSD.org">portmgr@FreeBSD.org</a>:
   &a.kris;, &a.marcus;, &a.linimon;, &a.eik;, &a.krion;</p>
 
 <p>Secretary: <!-- missing: &a.erwin; -->Erwin Lansing</p>
 
 <h3>Related Documentation</h3>
 
 <ul>
   <li>
     <p><a href="&base;/doc/en_US.ISO8859-1/books/porters-handbook/index.html">
       FreeBSD Porter's Handbook</a><br>
 
       <small>A general guide for FreeBSD ports committers, including both
 	technical information and policy guidelines.</small></p>
   </li>
 
 <!-- future document: "Rights And Responsibilities of FreeBSD Ports
   Maintainers and Committers" -->
 
   <li>
     <p><a href="http://pointyhat.FreeBSD.org">FreeBSD Ports Build
       Cluster</a><br>
 
       <small>These machines continually build packages on all possible
 	combinations of OS release and CPU architecture (in our terminology,
 	<tt>build environments</tt>), and produce error logs of problems
 	that are encountered along the way.</small></p>
   </li>
 
   <li>
     <p><a
       href="&base;/doc/en_US.ISO8859-1/articles/portbuild/index.html">
       FreeBSD Package Building Procedures</a><br>
 
       <small>Describes the technical operation of the build cluster.</small>
     </p>
   </li>
 
   <li>
     <p><a
       href="&base;/doc/en_US.ISO8859-1/articles/releng-packages/index.html">
       FreeBSD Release Engineering for Third Party Packages</a><br>
 
       <small>Describes the approach used by the FreeBSD release
 	engineering team to produce a high quality package set
 	suitable for official FreeBSD release media, with specific
 	emphasis on how to split up the packages for the release
 	media, and how to verify that a package set is
 	consistent.</small></p>
   </li>
 
   <!-- arguably the following should be added here:
     portsmon; FreshPorts; fenner's list; PR statistics; GNATS -->
 
   <li>
     <p><a
       href="&base;/doc/en_US.ISO8859-1/articles/committers-guide/index.html">
 	FreeBSD Committer's Guide</a><br>
 
       <small>Includes a discussion of policies and issues that are particular
 	interest to committers to the ports tree.</small></p>
   </li>
 
   <li>
     <p><a href="&base;/doc/en_US.ISO8859-1/books/pr-guidelines/index.html">
       Problem Report Handling Guidelines</a><br>
 
       <small>While primarily aimed at FreeBSD committers, this should
 	also be read by users interested in how best to attract attention
 	to their PRs.</small></p>
   </li>
 
 </ul>
 
 &footer;
 </body>
 </html>
