--- a/contacts/tests/Overview.html	Wed May 25 17:14:43 2011 +0200
+++ b/contacts/tests/Overview.html	Wed May 25 17:22:23 2011 +0200
@@ -215,9 +215,7 @@
  <p>This document provides an overview of the test suite for the <a
    href="http://www.w3.org/TR/contacts-api/">Contacts API</a>  specification. The Working Group
 has developed this test suite so to have a test case for every conformance requirement in the specification. </p>
- <p><strong>Please note that this document puts a number <a href="requirements">requirements</a> on user agents, which must be supported in order to be able to run the tests. </strong></p>
- <p>The keywords <dfn title=""><em class="ct-samp">must</em></dfn>, <dfn title=""><em class="ct-samp">must not</em></dfn>, <dfn title=""><em class="ct-samp">should</em></dfn>, <dfn title=""><em class="ct-samp">recommended</em></dfn>, <dfn title=""><em class="ct-samp">may</em></dfn> and <dfn title=""><em class=
-  "ct-samp">optional</em></dfn> in this document are to be interpreted as described in <span>[RFC2119]</span>.</p>
+
  <h2>Status of this Test Suite</h2>
  <p>Publication of this test suite does not imply endorsement by the W3C Membership. This   test suite is constantly evolving and the tests within in may be updated, replaced or obsoleted by other test at any time. When new tests become available, old obsoleted tests should be discarded. It is inappropriate to cite this document as other than a work in progress.</p>
 <h2>Licenses and Contributions</h2>
@@ -234,31 +232,11 @@
 <p>This specification adheres to the guidelines described in  <cite><a href="http://www.w3.org/TR/test-methodology/">A Method for Writing Testable Conformance Requirements</a></cite>. Please refer to that document for terminology and the approach that was taken to create this test suite. </p>
 
 <p>The JavaScript-based tests rely on the <a href="http://w3c-test.org/resources/testharness.js">common JavaScript Test Harness</a> used by other Working Groups.</p>
-<h2 id="requirements">User Agent Requirements
-</h2>
- <p>In addition to the specifications required to be supported by user
-   agents by the P&amp;C specification, some tests require, at a minimum,
-</p>
- <ul>
-   <li><span>[HTML4.01]</span>
-     <ul>
-       <li>Although the HTML-based tests templates are written to conform to
-         the <a href="#html5">[HTML]</a> specification, the templates are
-         compatible with <span>[HTML4.01]</span>.</li>
-     </ul>
-   </li>
-   <li><span>[CSS1]</span>
-     <ul>
-       <li>The <code>background-color</code> property and the colors: <code>red</code>, <code>green</code>, and <code>#666</code>.</li>
-     </ul>
-   </li>
- </ul>
- <p>Without support for the above specifications, it may not be possible for a user agent to effectively run the test cases of the test suite (and false results may occur). 
-</p>
+
 <h2 id="how-to-write-a-test">Automated testing</h2>
 <p>The Working Group does not provide an automated testing solution for
    this specification. However, every test case in the test suite is
-  available through the W3C's CVS repository.</p>
+  available through the W3C Mercurial repository.</p>
 <h2>How to get the tests and test descriptions</h2>
 <p><strong>Before you run the tests, please make sure you read this document thoroughly.</strong></p>
 <p>Tests can be downloaded using Mercurial using the following commands:</p>