diff --git a/xep-0157.xml b/xep-0157.xml
index f3dfd370..64a94a1f 100644
--- a/xep-0157.xml
+++ b/xep-0157.xml
@@ -10,7 +10,7 @@
   <abstract>This document defines a method for specifying contact addresses related to an XMPP service.</abstract>
   &LEGALNOTICE;
   <number>0157</number>
-  <status>Proposed</status>
+  <status>Active</status>
   <type>Informational</type>
   <sig>Standards</sig>
   <approver>Council</approver>
@@ -21,6 +21,12 @@
   <supersededby/>
   <shortname>N/A</shortname>
   &stpeter;
+  <revision>
+    <version>1.0</version>
+    <date>2007-01-31</date>
+    <initials>psa</initials>
+    <remark><p>Per a vote of the XMPP Council, advanced specification to Active.</p></remark>
+  </revision>
   <author>
     <firstname>Jacek</firstname>
     <surname>Konieczny</surname>
@@ -77,8 +83,7 @@
   </revision>
 </header>
 <section1 topic='Introduction' anchor='intro'>
-  &RFC3920BISNOTE;
-  <p>&rfc2142; specifies conventional electronic mailbox names for common services, roles, and functions related to SMTP, NNTP, and HTTP (such as postmaster@domain.tld, usenet@domain.tld, and webmaster@domain.tld). However, no such conventional email address or XMPP address (JID) has been specified for XMPP services. This document remedies that oversight.</p>
+  <p>&rfc2142; specifies conventional electronic mailbox names for common services, roles, and functions related to SMTP, NNTP, and HTTP (such as hostmaster@domain.tld, usenet@domain.tld, and abuse@domain.tld). However, no such conventional email address or XMPP address has been specified for XMPP services (e.g., in &rfc3920;). This document remedies that oversight.</p>
 </section1>
 <section1 topic='Email Address' anchor='email'>
   <p>Consistent with <cite>RFC 2142</cite>, a domain that offers a Jabber/XMPP service SHOULD provide an Internet mailbox of "XMPP" for inquiries related to that service.</p>
@@ -149,7 +154,7 @@
   <p>This document requires no interaction with &IANA;.</p>
 </section1>
 <section1 topic='XMPP Registrar Considerations' anchor='registrar'>
-  <p>The &REGISTRAR; shall include the following information in its registries.</p>
+  <p>The &REGISTRAR; includes the following information in its registries.</p>
   <section2 topic='Field Standardization' anchor='registrar-formtype'>
     <p>&xep0068; defines a process for standardizing the fields used within Data Forms qualified by a particular namespace, and <cite>XEP-0128</cite> describes how to use field standardization in the context of service discovery. This section registers fields for server information scoped by the "http://jabber.org/network/serverinfo" FORM_TYPE.</p>
     <code caption='Registry Submission'><![CDATA[