From 3a01bc946a5a802400c8adcac8418123b41aee04 Mon Sep 17 00:00:00 2001
From: Mike Gower <michael.gower@ca.ibm.com>
Date: Fri, 17 Oct 2025 07:47:53 -0700
Subject: [PATCH 1/6] Update error-identification.html

---
 understanding/20/error-identification.html | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/understanding/20/error-identification.html b/understanding/20/error-identification.html
index d1989bb2ce..5486e318c7 100644
--- a/understanding/20/error-identification.html
+++ b/understanding/20/error-identification.html
@@ -25,10 +25,9 @@ <h2>Intent of Error Identification</h2>
          has occurred and can determine what is wrong. In the case of an unsuccessful form submission,
          it is not sufficient to only re-display the form without providing any hint that the submission
          failed.
-         The error must be indicated in <a>text</a>.
-         Whether or not an error message provides users with sufficient information about the nature of
-         the error, and what they should do to correct it, is covered more specifically by
-         <a href="error-suggestion">3.3.3 Error Suggestion</a>.
+         The error must be indicated in <a>text</a>.</p>
+         <p>This SC requires that users be provided with information about the nature of the error, including the identity of the item in error. What the user should do to correct the item in error is covered by 
+         <a href="error-suggestion">3.3.3 Error Suggestion</a>. Often, the error description can be phrased so that it meets both SC 3.3.1 and SC 3.3.3 simultaneously. For instance, "Please provide a valid email address" conveys that email the field is empty or invalid and also how it can be fixed.
       </p>
       <p>An "input error" is information provided by the user that is not accepted. This includes:</p>
 

From aa998cdaa5d2b6f50e5fbaa0a384da9fc4d395f0 Mon Sep 17 00:00:00 2001
From: Mike Gower <michael.gower@ca.ibm.com>
Date: Fri, 17 Oct 2025 07:51:34 -0700
Subject: [PATCH 2/6] Update error-identification.html

Adding second requested change in the document
---
 understanding/20/error-identification.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/understanding/20/error-identification.html b/understanding/20/error-identification.html
index 5486e318c7..e1a92ff055 100644
--- a/understanding/20/error-identification.html
+++ b/understanding/20/error-identification.html
@@ -29,7 +29,7 @@ <h2>Intent of Error Identification</h2>
          <p>This SC requires that users be provided with information about the nature of the error, including the identity of the item in error. What the user should do to correct the item in error is covered by 
          <a href="error-suggestion">3.3.3 Error Suggestion</a>. Often, the error description can be phrased so that it meets both SC 3.3.1 and SC 3.3.3 simultaneously. For instance, "Please provide a valid email address" conveys that email the field is empty or invalid and also how it can be fixed.
       </p>
-      <p>An "input error" is information provided by the user that is not accepted. This includes:</p>
+      <p>An "input error" is input data that has failed validation for the application, preventing access to further processing. This includes:</p>
 
       <ul>
          <li>information that is required by the web page but omitted by the user, or</li>

From b74781a7e843f599812e33434a67c9a4fb290b2a Mon Sep 17 00:00:00 2001
From: Mike Gower <mikegower@gmail.com>
Date: Fri, 17 Oct 2025 08:53:29 -0700
Subject: [PATCH 3/6] Update understanding/20/error-identification.html

---
 understanding/20/error-identification.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/understanding/20/error-identification.html b/understanding/20/error-identification.html
index e1a92ff055..4674e2dbe3 100644
--- a/understanding/20/error-identification.html
+++ b/understanding/20/error-identification.html
@@ -27,7 +27,7 @@ <h2>Intent of Error Identification</h2>
          failed.
          The error must be indicated in <a>text</a>.</p>
          <p>This SC requires that users be provided with information about the nature of the error, including the identity of the item in error. What the user should do to correct the item in error is covered by 
-         <a href="error-suggestion">3.3.3 Error Suggestion</a>. Often, the error description can be phrased so that it meets both SC 3.3.1 and SC 3.3.3 simultaneously. For instance, "Please provide a valid email address" conveys that email the field is empty or invalid and also how it can be fixed.
+         <a href="error-suggestion">3.3.3 Error Suggestion</a>. Often, the error description can be phrased so that it meets both SC 3.3.1 and SC 3.3.3 simultaneously. For instance, "Please provide a valid email address" conveys that the email field is empty or invalid and also how it can be fixed.
       </p>
       <p>An "input error" is input data that has failed validation for the application, preventing access to further processing. This includes:</p>
 

From 5f68b04e693c669b8c0951131f873cdc32da4842 Mon Sep 17 00:00:00 2001
From: Mike Gower <mikegower@gmail.com>
Date: Fri, 17 Oct 2025 08:55:27 -0700
Subject: [PATCH 4/6] Update understanding/20/error-identification.html

---
 understanding/20/error-identification.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/understanding/20/error-identification.html b/understanding/20/error-identification.html
index 4674e2dbe3..95d29c3866 100644
--- a/understanding/20/error-identification.html
+++ b/understanding/20/error-identification.html
@@ -27,7 +27,7 @@ <h2>Intent of Error Identification</h2>
          failed.
          The error must be indicated in <a>text</a>.</p>
          <p>This SC requires that users be provided with information about the nature of the error, including the identity of the item in error. What the user should do to correct the item in error is covered by 
-         <a href="error-suggestion">3.3.3 Error Suggestion</a>. Often, the error description can be phrased so that it meets both SC 3.3.1 and SC 3.3.3 simultaneously. For instance, "Please provide a valid email address" conveys that the email field is empty or invalid and also how it can be fixed.
+         <a href="error-suggestion">3.3.3 Error Suggestion</a>. Often, the error description can be phrased so that it meets both SC 3.3.1 and SC 3.3.3 at the same time. For instance, "Please provide a valid email address" conveys that the email field is empty or invalid, and also how it can be fixed.
       </p>
       <p>An "input error" is input data that has failed validation for the application, preventing access to further processing. This includes:</p>
 

From e20b5bab6df8bf898f09a4f38e809d06db405a32 Mon Sep 17 00:00:00 2001
From: Mike Gower <mikegower@gmail.com>
Date: Fri, 17 Oct 2025 08:58:28 -0700
Subject: [PATCH 5/6] Update understanding/20/error-identification.html

---
 understanding/20/error-identification.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/understanding/20/error-identification.html b/understanding/20/error-identification.html
index 95d29c3866..48cf9f7283 100644
--- a/understanding/20/error-identification.html
+++ b/understanding/20/error-identification.html
@@ -29,7 +29,7 @@ <h2>Intent of Error Identification</h2>
          <p>This SC requires that users be provided with information about the nature of the error, including the identity of the item in error. What the user should do to correct the item in error is covered by 
          <a href="error-suggestion">3.3.3 Error Suggestion</a>. Often, the error description can be phrased so that it meets both SC 3.3.1 and SC 3.3.3 at the same time. For instance, "Please provide a valid email address" conveys that the email field is empty or invalid, and also how it can be fixed.
       </p>
-      <p>An "input error" is input data that has failed validation for the application, preventing access to further processing. This includes:</p>
+      <p>An "input error" is input data that has failed validation. This includes:</p>
 
       <ul>
          <li>information that is required by the web page but omitted by the user, or</li>

From a6eb37cdbdf77fdd257e54c2e6c6203aa907dc70 Mon Sep 17 00:00:00 2001
From: Mike Gower <mikegower@gmail.com>
Date: Fri, 31 Oct 2025 08:42:54 -0700
Subject: [PATCH 6/6] Update understanding/20/error-identification.html

Looked at on TF call
---
 understanding/20/error-identification.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/understanding/20/error-identification.html b/understanding/20/error-identification.html
index 48cf9f7283..38f9aea470 100644
--- a/understanding/20/error-identification.html
+++ b/understanding/20/error-identification.html
@@ -29,7 +29,7 @@ <h2>Intent of Error Identification</h2>
          <p>This SC requires that users be provided with information about the nature of the error, including the identity of the item in error. What the user should do to correct the item in error is covered by 
          <a href="error-suggestion">3.3.3 Error Suggestion</a>. Often, the error description can be phrased so that it meets both SC 3.3.1 and SC 3.3.3 at the same time. For instance, "Please provide a valid email address" conveys that the email field is empty or invalid, and also how it can be fixed.
       </p>
-      <p>An "input error" is input data that has failed validation. This includes:</p>
+      <p>An "input error" includes:</p>
 
       <ul>
          <li>information that is required by the web page but omitted by the user, or</li>