just capitalization fix (#3154)

<!--
    This comment and the below content is programmatically generated.
    You may add a comma-separated list of anchors you'd like a
    direct link to below (e.g. #idl-serializers, #idl-sequence):

    Don't remove this comment or modify anything below this line.
    If you don't want a preview generated for this pull request,
    just replace the whole of this comment's content by "no preview"
    and remove what's below.
-->
***
<a href="https://pr-preview.s3.amazonaws.com/w3c/wcag/pull/3154.html"
title="Last updated on Sep 16, 2024, 4:34 PM UTC (dc219d3)">Preview</a>
| <a
href="https://pr-preview.s3.amazonaws.com/w3c/wcag/3154/b24abad...dc219d3.html"
title="Last updated on Sep 16, 2024, 4:34 PM UTC (dc219d3)">Diff</a>

Co-authored-by: Patrick H. Lauke <redux@splintered.co.uk>

Author: shawna-slh

guidelines/sc/20/parsing.html

@@ -10,14 +10,14 @@ <h4>Parsing</h4>
       these features.
    </p>
 
-   <p class="note">This Success Criterion should be considered as always satisfied for any content using HTML or XML.</p>
+   <p class="note">This success criterion should be considered as always satisfied for any content using HTML or XML.</p>
 
    <div class="note">
       <p>Since this criterion was written, the HTML Living Standard has adopted specific requirements governing how user agents must handle incomplete tags, incorrect element nesting, duplicate attributes, and non-unique IDs. [[HTML]]</p>
 
-      <p>Although the HTML Standard treats some of these cases as non-conforming for authors, it is considered to "allow these features" for the purposes of this Success Criterion because the specification requires that user agents support handling these cases consistently. In practice, this criterion no longer provides any benefit to people with disabilities in itself.</p>
+      <p>Although the HTML standard treats some of these cases as non-conforming for authors, it is considered to "allow these features" for the purposes of this success criterion because the specification requires that user agents support handling these cases consistently. In practice, this criterion no longer provides any benefit to people with disabilities in itself.</p>
 
-      <p>Issues such as missing roles due to inappropriately nested elements or incorrect states or names due to a duplicate ID are covered by different Success Criteria and should be reported under those criteria rather than as issues with 4.1.1.</p>
+      <p>Issues such as missing roles due to inappropriately nested elements or incorrect states or names due to a duplicate ID are covered by different success criteria and should be reported under those criteria rather than as issues with 4.1.1.</p>
    </div>
 
 </section>