Catchup PR (#736)

* Resolving issue 307 (minutes 27th Feb)

* Updating motivation

https://www.w3.org/2024/02/27-ag-minutes#item05

* Addressing #371

requirements/index.html

@@ -186,15 +186,16 @@ <h2 id="design_principles">Design Principles</h2>
             <li>Be accessible and conform to the Guidelines. <span class="ednote">Note: This design principle will move to the Requirements section once the Conformance section is completed and we determine a specific measurement of compliance. </span></li>
             <li>Be written in plain language, as easy as possible to understand. <span class="ednote"> We need a definition of plain language that includes the ease of translation. Ideally, it will be a broadly accepted definition internationally. </span></li>
 			<li>Improve the ability to support automated testing where appropriate and provide a procedure for repeatable tests when manual testing is appropriate.</li>
-						<li>Provide requirements to address functional needs, while avoiding or minimizing negative impacts on other functional needs. </li>
+			<li>Provide requirements to address functional needs, while avoiding or minimizing negative impacts on other functional needs. </li>
+			<li>Include accompanying documents that provide clear, concise, and findable technical information quickly in one place.</li>
+			<li>Normative requirements should be unambiguous so there is only one possible meaning for each requirement.</li>
           </ol>
           <p>The creation process for the guidelines should:</p>
           <ol start="7">
             <li>Actively recruit a diverse range of people with disabilities in recognition of the importance of their contributions to accessibility standards and solutions. Review and monitor whether people are included. Continually evaluate inclusive features of available tooling and procedures. </li>
             <li>Facilitate global participation and feedback.</li>
             <li>Be data-informed and evidence-based where possible.  We recognize that research and evidence are influenced by the number of people with a particular disability, by the size of the body of research, and by the difficulty in capturing data regarding some disabilities or combination of disabilities.  The intent is to make informed decisions wherever possible to ensure that the needs of all people with disabilities are prioritized, including needs that differ from the majority. In situations where there is no evidence or research, valid data-gathering methods should be used to obtain and evaluate information from advocacy groups, people with lived experience and other subject matter experts.</li>
-			<li>Be written so the Guideline content is usable in adaptable and customizable ways. For example, WCAG 3.0 content is available to be extracted by users to adapt to their needs. </li>
-
+			<li>Be written so the Guideline content is usable in adaptable and customizable ways. For example, WCAG 3.0 content is available to be extracted by users to adapt to their needs. </li>			
           </ol>
 </section>
 		<section>
@@ -232,7 +233,7 @@ <h3>Regulatory Environment</h3>
 	  </section>
           <section>
             <h3>Motivation</h3>
-	    <p>The Guidelines motivate organizations to go beyond minimal accessibility requirements by providing a scoring system that rewards organizations which demonstrate a greater effort to improve accessibility.</p>
+	    <p>The Guidelines motivate organizations to go beyond minimal accessibility requirements by structuring WCAG 3 to provide encouragement to organizations which demonstrate a greater effort to improve accessibility.</p>
 	 </section>
           <section>
             <h3>Scope</h3>