Gregg's suggestions from thread in #739

Author: alastc

requirements/index.html

@@ -113,7 +113,7 @@ <h4>Usability</h4>
 					<h4>Conformance Model</h4>
 					<p>There are several areas for exploration in how conformance can work. These opportunities may or may not be incorporated. They need to work together, and that interplay will be governed by the design principles</p>
 					<ul>
-						<li><strong>Measurable Guidance</strong>: Certain accessibility guidance is best expressed as a true/false statement. Others far less so. There are needs of people with disabilities, especially cognitive and low vision disabilities, that are better captured by a different type of measurement. WCAG 3.0 can include multiple means of measurement, in addition to true/false statements, allowing inclusion of more accessibility guidance.</li>
+						<li><strong>Measurable Guidance</strong>: Certain accessibility guidance is best expressed as a true/false statement. Others far less so. There are needs of people with disabilities, especially cognitive and low vision disabilities, that are better captured by a different type of measurement. WCAG 3.0 can include guidance (provisions) that use different means of evaluation beyond just true/false performance or outcome statements, allowing for the inclusion of more accessibility guidance.</li>
 						<li><strong>Scope Options</strong>: WCAG 3.0 conformance could include web pages, web sites, page sections, individual components, and conformance based on a set of tasks as defined by the author of the site or application. A task-based assessment would allow flexibility for conformance of complex applications that go beyond component/tag assessment or full-page assessment.</li>
 						<li><strong>Accessibility Supported</strong>: As the technologies advance, the lines between content, user agents, and assistive technology will continue to shift and blur. Interoperability may be affected by any number of factors outside of the control of the author and publisher of digital content. WCAG 3.0 can include advice to user agents and assistive technology developers. WCAG 3 does not intend to make authors responsible for interoperability problems beyond a reasonable effort.</li>
 					</ul>
@@ -236,12 +236,16 @@ <h3>Regulatory Environment</h3>
             <h3>Motivation</h3>
 	    <p>The Guidelines motivate organizations to go beyond minimal accessibility requirements with a conformance model that shows which organizations demonstrate a greater effort to improve accessibility</p>
 	 </section>
-          <section>
+        <section>
             <h3>Scope</h3>
 	    <p>WCAG 3 will provide guidance and a conformance model suitable for people and organizations that produce digital assets and technology of varying size and complexity. This includes large, dynamic, and complex websites. The scope of the associated informative materials will include guidance for a diverse group of stakeholders including content creators, browsers, authoring tools, assistive technologies, and more.</p>
 
-	</section>
 		</section>
+		<section>
+			<h3>Self validation</h3>
+			<p>The WCAG 3 guidelines document shall meet all of its own requirements.</p>
+		</section>
+	</section>
 		<section class="appendix" id="changelog">
 	    <h2>Change Log</h2>
           <section>