Fix validation issues

comments-by-guideline-and-success-criterion.md

@@ -484,7 +484,7 @@ With these substitutions, it would read:
 <dd>For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to <a href="https://www.w3.org/TR/WCAG22/#dfn-pause)">pause</a>, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is <a href="https://www.w3.org/TR/WCAG22/#dfn-essential">essential</a>; and</dd>
 
 <dt>Auto-updating</dt>
-<dd></dd>For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.</dd>
+<dd>For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.</dd>
 </dl>
 
 <div class="note">

introduction.md

@@ -111,7 +111,7 @@ The following changes and additions have been made to update the 2013 WCAG2ICT d
         * [target](#dfn-targets)
         * [up event](#dfn-up-event)
 * Updated terms
-    * [large scale](#large-scale)
+    * [large scale](#dfn-large-scale)
     * [set of web pages](#dfn-set-of-web-pages)
     * [set of non-web documents](#set-of-documents)
     * [set of software programs](#set-of-software-programs)

wcag.json

@@ -742,7 +742,7 @@
                             "num": "4.1.1",
                             "handle": "Parsing (WCAG 2.1)",
                             "level": "(Level A)",
-                            "content": "  <p>In content implemented using markup languages, elements have complete start and end       tags, elements are nested according to their specifications, elements do not contain       duplicate attributes, and any IDs are unique, except where the specifications allow       these features.    </p>   <div class=\"note\" id=\"issue-container-generatedID-26\" role=\"note\"><div aria-level=\"5\" class=\"note-title marker\" id=\"h-note-26\" role=\"heading\"><span>Note</span></div><p class=\"\">This Success Criterion should be considered as always satisfied for any content using HTML or XML.</p></div>   <div class=\"note\" id=\"issue-container-generatedID-27\" role=\"note\"><div aria-level=\"5\" class=\"note-title marker\" id=\"h-note-27\" role=\"heading\"><span>Note</span></div><div class=\"\"> <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. [<cite><a class=\"bibref\" data-link-type=\"biblio\" href=\"#bib-html\" title=\"HTML Standard\">HTML</a></cite>]</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> </div></div>  "
+                            "content": "  <p>In content implemented using markup languages, elements have complete start and end       tags, elements are nested according to their specifications, elements do not contain       duplicate attributes, and any IDs are unique, except where the specifications allow       these features.    </p>   <div class=\"note\" id=\"issue-container-generatedID-26\" role=\"note\"><div aria-level=\"5\" class=\"note-title marker\" id=\"h-note-26\" role=\"heading\"><span>Note</span></div><p class=\"\">This Success Criterion should be considered as always satisfied for any content using HTML or XML.</p></div>   <div class=\"note\" id=\"wcag21-issue-container-generatedID-27\" role=\"note\"><div aria-level=\"5\" class=\"note-title marker\" id=\"wca21-h-note-27\" role=\"heading\"><span>Note</span></div><div class=\"\"> <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. [<cite><a class=\"bibref\" data-link-type=\"biblio\" href=\"#bib-html\" title=\"HTML Standard\">HTML</a></cite>]</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> </div></div>  "
                         },
                         {
                             "id": "parsing22",