cleanup

guidelines/index.html

@@ -192,19 +192,19 @@ <h2>Conformance</h2>
 			<details class="summary">
 				<summary>Summary</summary>
 				<p>You might want to make a claim that your content or product meets the WCAG 3 guidelines. If it does meet the guidelines, we call this “conformance.” To conform to WCAG 3, your test results must show that your project is accessible.</p>
-				<p>If you want to make a conformance claim, you must use the process described in this document. However, conformance claims are not required and your content can conform to WCAG 3, even if you don’t want to make a claim. You can still use this process to test your project’s accessibility.</p>	
+				<p>If you want to make a formal conformance claim, you must use the process described in this document. However, conformance claims are not required and your content can conform to WCAG 3, even if you don’t want to make a claim. You can still use this process to test your project’s accessibility.</p>	
 				<p>There are two types of content in this document:</p>
 				<ul>
 					<li><strong>Normative:</strong> what you must do to meet the guidelines.</li>
-					<li><strong>Non-normative:</strong> advice to help you meet the guidelines. This is also called <q>Informative</q>.</li>
+					<li><strong>Non-normative:</strong> advice to help you meet the guidelines. This is also called <q>informative</q>.</li>
 				</ul>
-				<p>There are a variety of ways to say what is required in WCAG 3.  We are experimenting with different approaches.  Once we have developed enough guidelines, we will test how well each works.  Here are some of the ideas for WCAG 3 requirements. </p>
+				<p>There are a variety of ways to say what is required in WCAG 3. We are experimenting with different approaches. Once we have developed enough guidelines, we will test how well each works. Here are some of the ideas for WCAG 3 requirements:</p>
 				<ul>
 					<li>Two ways of testing accessibility 
 					<ul><li>Outcomes are statements that can be tested.</li>
 						<li>Assertions and procedures are statements that you used an accessible way to create the content that is hard to test.  Assertions are new and we are trying different rules for how they can work. </li>
 					</ul></li>
-					<li>Three different levels show how accessible the content is: bronze, silver, or gold level</li>
+					<li>Three different levels show how accessible the content is: bronze, silver, or gold level.</li>
 					<li>Issue severity allows different rules for accessibility problems. Rules for problems that block people from using the content are stronger than rules for minor problems. </li>
 					<li>Adjectival ratings allow testers to grade content using words (fail, pass, great) or numbers (1,2,3). This provides a scale that may better match what people with disabilities go through to use it. </li>
 					<li>Percentages are used instead of requiring that accessibility be perfect or you fail.  </li>