From 689cef8a60c262dbee8a139e4f9689b639257e5b Mon Sep 17 00:00:00 2001
From: "Patrick H. Lauke" <redux@splintered.co.uk>
Date: Thu, 4 Aug 2022 12:20:49 +0100
Subject: [PATCH] Expand explanation of "repair techniques"

Closes https://github.com/w3c/wcag/issues/2563
---
 understanding/20/parsing.html | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/understanding/20/parsing.html b/understanding/20/parsing.html
index 0abdadd950..51da914337 100644
--- a/understanding/20/parsing.html
+++ b/understanding/20/parsing.html
@@ -22,7 +22,8 @@ <h2>Intent of Parsing</h2>
          
       </p>
       
-      <p>Since repair techniques vary among user agents, authors cannot assume that content
+      <p>Since these repair techniques - the way user agents will attempt to parse and error-correct
+         malformed or invalid markup - may vary among user agents, authors cannot assume that content
          will be accurately parsed into a data structure or that it will be rendered correctly
          by specialized user agents, including assistive technologies, unless the content is
          created according to the rules defined in the formal grammar for that technology.
@@ -38,7 +39,7 @@ <h2>Intent of Parsing</h2>
          
          <p>The concept of "well formed" is close to what is required here. However, exact parsing
             requirements vary amongst markup languages, and most non XML-based languages do not
-            explicitly define requirements for well formedness. Therefore, it was necessary to
+            explicitly define requirements for well-formedness. Therefore, it was necessary to
             be more explicit in the success criterion in order to be generally applicable to markup
             languages. Because the term "well formed" is only defined in XML, and (because end
             tags are sometimes optional) valid HTML does not require well formed code, the term