diff --git a/accessibility-checker-engine/help-v4/en-US/a_target_warning.html b/accessibility-checker-engine/help-v4/en-US/a_target_warning.html
index 66fe073ba..6be908f45 100644
--- a/accessibility-checker-engine/help-v4/en-US/a_target_warning.html
+++ b/accessibility-checker-engine/help-v4/en-US/a_target_warning.html
@@ -54,7 +54,7 @@ <h3 id="ruleMessage"></h3>
 ### What to do
 
 * Include a warning in the label advising the user that the link opens in a new window
-* **Or**, use CSS to provide a warning before opening a new window (see Example 2 in [G201](https://www.w3.org/WAI/WCAG22/Techniques/general/G201))
+* **Or**, use CSS to provide a warning before opening a new window (see Example 2 in [WCAG technique G201](https://www.w3.org/WAI/WCAG22/Techniques/general/G201))
 
 </script></mark-down>
 <!-- End main panel -->
diff --git a/accessibility-checker-engine/help-v4/en-US/a_text_purpose.html b/accessibility-checker-engine/help-v4/en-US/a_text_purpose.html
index 89fae66f9..db671ef74 100644
--- a/accessibility-checker-engine/help-v4/en-US/a_text_purpose.html
+++ b/accessibility-checker-engine/help-v4/en-US/a_text_purpose.html
@@ -53,8 +53,8 @@ <h3 id="ruleMessage"></h3>
 ### What to do
 
 * Ideally, add unique link text as the content of the hyperlink that describes the purpose of the hyperlink
-* **Or**, if it’s not possible to use unique link text (e.g. multiple ‘Read more..’ links for different topics), use the `aria-labelledby` attribute to point to text visible on the page that identifies the link purpose.
-The following example shows how the `aria-labelledby` provides additional context by adding the text 'Breaking News' from the header to the link text 'Read more..':
+* **Or**, if it’s not possible to use unique link text (e.g., multiple ‘Read more.’ links for different topics), use the `aria-labelledby` attribute to point to text visible on the page that identifies the link purpose.
+The following example shows how the `aria-labelledby` provides additional context by adding the text 'Breaking News' from the header to the link text 'Read more.':
 
 ### Example
 
@@ -62,7 +62,7 @@ <h3 id="ruleMessage"></h3>
 <h2 id="topic1">Breaking News</h2>
 <p>
     The central bank cut interest rates by half a
-    percentage to protect economy.
+    percentage to protect the economy.
     <a
         id="p1"
         href="news.html"
diff --git a/accessibility-checker-engine/help-v4/en-US/aria_activedescendant_tabindex_valid.html b/accessibility-checker-engine/help-v4/en-US/aria_activedescendant_tabindex_valid.html
index b35786a02..d392f17ec 100644
--- a/accessibility-checker-engine/help-v4/en-US/aria_activedescendant_tabindex_valid.html
+++ b/accessibility-checker-engine/help-v4/en-US/aria_activedescendant_tabindex_valid.html
@@ -53,7 +53,7 @@ <h3 id="ruleMessage"></h3>
 The `tabindex` value defines the order (sequence) in which elements will receive focus when users navigate via the keyboard:
 * `"-1"` will remove the element from the tab sequence (ignored during tabbing) but may remain focusable
 * `"0"` will be handled in the order (tab sequence) as it appears in the DOM source code order
-* `">0"` (positive number) [creates a relative ordering](https://html.spec.whatwg.org/multipage/interaction.html#the-tabindex-attribute) that starts from the element(s) with the lowest value (e.g. 1) and then proceeds to the element(s) with the next higher value
+* `">0"` (positive number) [creates a relative ordering](https://html.spec.whatwg.org/multipage/interaction.html#the-tabindex-attribute) that starts from the element(s) with the lowest value (e.g., 1) and then proceeds to the element(s) with the next higher value
 
 <!-- This is where the code snippet is injected -->
 <div id="locSnippet"></div>
diff --git a/accessibility-checker-engine/help-v4/en-US/aria_content_in_landmark.html b/accessibility-checker-engine/help-v4/en-US/aria_content_in_landmark.html
index d22218fd9..ee6cde7e5 100644
--- a/accessibility-checker-engine/help-v4/en-US/aria_content_in_landmark.html
+++ b/accessibility-checker-engine/help-v4/en-US/aria_content_in_landmark.html
@@ -52,8 +52,8 @@ <h3 id="ruleMessage"></h3>
 
 ### What to do
 
-* Enclose the content within an HTML5 sectioning element with an implicit landmark role (e.g. `<main>Content</main>`);
-* **Or**, use the `"role"` attribute on an enclosing element to specify an appropriate ARIA landmark value (e.g. `<div role="contentinfo">...</div>`).
+* Enclose the content within an HTML5 sectioning element with an implicit landmark role (e.g., `<main>Content</main>`);
+* **Or**, use the `"role"` attribute on an enclosing element to specify an appropriate ARIA landmark value (e.g., `<div role="contentinfo">...</div>`).
 
 </script></mark-down>
 <!-- End main panel -->
diff --git a/accessibility-checker-engine/help-v4/en-US/aria_main_label_unique.html b/accessibility-checker-engine/help-v4/en-US/aria_main_label_unique.html
index 6e491120c..26a6aa774 100644
--- a/accessibility-checker-engine/help-v4/en-US/aria_main_label_unique.html
+++ b/accessibility-checker-engine/help-v4/en-US/aria_main_label_unique.html
@@ -45,7 +45,7 @@ <h3 id="ruleMessage"></h3>
 
 ### Why is this important?
 
-The `<main>` element has an implicit landmark role of `"main"` that represents the central topic of the document. This provides a non-obtrusive alternative for a “skip to main content” link. It is possible, but not desirable, to have more than one element with a `"main"` role, for example through DOM nesting (e.g. a document within a document) or by use of the `aria-owns` attribute. In this situation, an associated unique label that describes each area of main content is needed to allow users of assistive technologies to understand the purpose of each main area, and navigate to them. Ideally the author SHOULD mark no more than one element with the `"main"` role.
+The `<main>` element has an implicit landmark role of `"main"` that represents the central topic of the document. This provides a non-obtrusive alternative for a “skip to main content” link. It is possible, but not desirable, to have more than one element with a `"main"` role, for example through DOM nesting (e.g., a document within a document) or by use of the `aria-owns` attribute. In this situation, an associated unique label that describes each area of main content is needed to allow users of assistive technologies to understand the purpose of each main area, and navigate to them. Ideally the author SHOULD mark no more than one element with the `"main"` role.
 
 <!-- This is where the code snippet is injected -->
 <div id="locSnippet"></div>
diff --git a/accessibility-checker-engine/help-v4/en-US/aria_widget_labelled.html b/accessibility-checker-engine/help-v4/en-US/aria_widget_labelled.html
index 9227e367c..066f3c1bf 100644
--- a/accessibility-checker-engine/help-v4/en-US/aria_widget_labelled.html
+++ b/accessibility-checker-engine/help-v4/en-US/aria_widget_labelled.html
@@ -54,7 +54,7 @@ <h3 id="ruleMessage"></h3>
 * Use the `aria-labelledby` attribute to reference existing visible text on the page that can clearly identify the purpose of the component;
 * **Or**, use the `aria-label` attribute with a short description as its value that can clearly identify the purpose of the component when a visual label is not available;
 * **Or**, use the `title` attribute to provide a name when the design cannot accommodate a visual label;
-* **Or**, if the element's role allows it to derive a label from its content, provide the label text as the inner content of the element (e.g. `<button type="submit">Search</button>`).
+* **Or**, if the element's role allows it to derive a label from its content, provide the label text as the inner content of the element (e.g., `<button type="submit">Search</button>`).
 
 The following code snippet shows a tree widget labelled with an `aria-labelledby` attribute to reference the heading text:
 
diff --git a/accessibility-checker-engine/help-v4/en-US/element_accesskey_labelled.html b/accessibility-checker-engine/help-v4/en-US/element_accesskey_labelled.html
index 750410e6f..cae8dd9a5 100644
--- a/accessibility-checker-engine/help-v4/en-US/element_accesskey_labelled.html
+++ b/accessibility-checker-engine/help-v4/en-US/element_accesskey_labelled.html
@@ -52,10 +52,10 @@ <h3 id="ruleMessage"></h3>
 
 ### What to do
 
- * Provide a label using a `title` attribute (e.g. `<a title="Activities" accesskey="A" href="/Consortium/activities">Activities</a>`);
+ * Provide a label using a `title` attribute (e.g., `<a title="Activities" accesskey="A" href="/Consortium/activities">Activities</a>`);
  * **Or**, use `<label for="">` or `aria-labelledby` to designate visible text as the label;
- * **Or**, use an input embedded in a `<label>` (e.g. `<label><input type="checkbox" accesskey="A"/>foo</label>`);
- * **Or**, if the element does not have a visible label, provide a label using the `aria-label` attribute (e.g. `aria-label="Activities"`).
+ * **Or**, use an input embedded in a `<label>` (e.g., `<label><input type="checkbox" accesskey="A"/>foo</label>`);
+ * **Or**, if the element does not have a visible label, provide a label using the `aria-label` attribute (e.g., `aria-label="Activities"`).
 
 </script></mark-down>
 <!-- End main panel -->
diff --git a/accessibility-checker-engine/help-v4/en-US/element_scrollable_tabbable.html b/accessibility-checker-engine/help-v4/en-US/element_scrollable_tabbable.html
index f16faab38..6e2209379 100644
--- a/accessibility-checker-engine/help-v4/en-US/element_scrollable_tabbable.html
+++ b/accessibility-checker-engine/help-v4/en-US/element_scrollable_tabbable.html
@@ -46,8 +46,8 @@ <h3 id="ruleMessage"></h3>
 ### Why is this important?
 
 Many users need to be able to use the keyboard and keyboard-like emulators to navigate to and operate scrollable elements – such as scrolling up-down and left-right with arrow keys – to reveal all the visible content. 
-Only some browsers (e.g. Firefox) will automatically include _**any**_ scrollable element in the tab-order (tabbable sequence) to ensure keyboard accessibility. 
-Browsers will automatically make scrollable elements tabbable when they _**contain**_ tabbable elements (e.g. buttons) without requiring an explicit `tabindex`attribute on the container element. 
+Only some browsers (e.g., Firefox) will automatically include _**any**_ scrollable element in the tab-order (tabbable sequence) to ensure keyboard accessibility. 
+Browsers will automatically make scrollable elements tabbable when they _**contain**_ tabbable elements (e.g., buttons) without requiring an explicit `tabindex`attribute on the container element. 
 However, setting the `tabindex` attribute on a scrollable container itself to a negative value excludes it and its tabbable content from the tab-order, 
 effectively making it keyboard inaccessible and blocking many users.
 
diff --git a/accessibility-checker-engine/help-v4/en-US/form_font_color.html b/accessibility-checker-engine/help-v4/en-US/form_font_color.html
index 787d8a36c..ade011e7c 100644
--- a/accessibility-checker-engine/help-v4/en-US/form_font_color.html
+++ b/accessibility-checker-engine/help-v4/en-US/form_font_color.html
@@ -52,7 +52,7 @@ <h3 id="ruleMessage"></h3>
 
 ### What to do
 
-* If color is used to indicate required fields, also use the `required` attribute and an asterisk ('*') with text (e.g.  “required fields are red") to indicate required fields both programmatically and visually without color;
+* If color is used to indicate required fields, also use the `required` attribute and an asterisk ('*') with text (e.g.,  “required fields are red") to indicate required fields both programmatically and visually without color;
 
 </script></mark-down>
 <!-- End main panel -->
diff --git a/accessibility-checker-engine/help-v4/en-US/html_lang_exists.html b/accessibility-checker-engine/help-v4/en-US/html_lang_exists.html
index 7c96a1619..5194946d7 100644
--- a/accessibility-checker-engine/help-v4/en-US/html_lang_exists.html
+++ b/accessibility-checker-engine/help-v4/en-US/html_lang_exists.html
@@ -52,7 +52,7 @@ <h3 id="ruleMessage"></h3>
 
 ### What to do
 
-* Identify the default language of the HTML document by providing the `lang` attribute on the HTML element (e.g. `<html lang="en">`);
+* Identify the default language of the HTML document by providing the `lang` attribute on the HTML element (e.g., `<html lang="en">`);
 * **Or**, if serving an XML document only (ie. using a MIME type such as application/xhtml+xml), identify the default language by providing the `xml:lang` attribute alone. The `lang` attribute is not needed (`<html xml:lang="fr" xmlns="https://www.w3.org/1999/xhtml">`)
 * **Or**, if serving XHTML 1.x or polyglot pages as text/html, use both the `lang` attribute and the `xml:lang` attribute and ensure the values for both attributes are identical (`<html lang="fr" xml:lang="fr" xmlns="https://www.w3.org/1999/xhtml">`)
 
diff --git a/accessibility-checker-engine/help-v4/en-US/html_skipnav_exists.html b/accessibility-checker-engine/help-v4/en-US/html_skipnav_exists.html
index 66c18fe9e..adfccd2f6 100644
--- a/accessibility-checker-engine/help-v4/en-US/html_skipnav_exists.html
+++ b/accessibility-checker-engine/help-v4/en-US/html_skipnav_exists.html
@@ -55,7 +55,7 @@ <h3 id="ruleMessage"></h3>
 * Provide headings for each content section using `<h1>` ... `<h6>`;
 * **And/or** provide landmarks to identify blocks of content on the page;
 * **And/or** use links to skip blocks of repeated content by linking from the top of the page to the main content, or from the start of the repeated content to the end of the block;
-* **And/or** group blocks of repeated content using structural elements (e.g. `<map>`, `<ul>` or `<ol>`), or `<frame>` elements with a `"title"` attribute, or an expandable and collapsible menu.
+* **And/or** group blocks of repeated content using structural elements (e.g., `<map>`, `<ul>` or `<ol>`), or `<frame>` elements with a `"title"` attribute, or an expandable and collapsible menu.
 
 </script></mark-down>
 <!-- End main panel -->
diff --git a/accessibility-checker-engine/help-v4/en-US/imagebutton_alt_exists.html b/accessibility-checker-engine/help-v4/en-US/imagebutton_alt_exists.html
index c805479ed..84cc13682 100644
--- a/accessibility-checker-engine/help-v4/en-US/imagebutton_alt_exists.html
+++ b/accessibility-checker-engine/help-v4/en-US/imagebutton_alt_exists.html
@@ -48,7 +48,7 @@ <h3 id="ruleMessage"></h3>
 
 ### What to do
 
-* Use the `alt` attribute on the `<input>` element to provide a short text that describes the input element’s function.(e.g. `<input type="image" alt="submit">`)
+* Use the `alt` attribute on the `<input>` element to provide a short text that describes the input element’s function.(e.g., `<input type="image" alt="submit">`)
 
 </script></mark-down>
 <!-- End main panel -->
diff --git a/accessibility-checker-engine/help-v4/en-US/img_alt_misuse.html b/accessibility-checker-engine/help-v4/en-US/img_alt_misuse.html
index 3a4c68d1e..f9000fed9 100644
--- a/accessibility-checker-engine/help-v4/en-US/img_alt_misuse.html
+++ b/accessibility-checker-engine/help-v4/en-US/img_alt_misuse.html
@@ -52,8 +52,8 @@ <h3 id="ruleMessage"></h3>
 
 ### What to do
 
-* If the image conveys meaning, the value of the `"alt"` attribute should be a short description that serves the same purpose as the image. Include any important words from the image in the short description (e.g. `<img alt="submit">`). Do not use a file name;
-* **Or**, if the image is decorative or the same information is also available in text, use the `"alt"` attribute with an empty string as its value (e.g.  `<img alt="">`).
+* If the image conveys meaning, the value of the `"alt"` attribute should be a short description that serves the same purpose as the image. Include any important words from the image in the short description (e.g., `<img alt="submit">`). Do not use a file name;
+* **Or**, if the image is decorative or the same information is also available in text, use the `"alt"` attribute with an empty string as its value (e.g.,  `<img alt="">`).
 
 </script></mark-down>
 <!-- End main panel -->
diff --git a/accessibility-checker-engine/help-v4/en-US/img_alt_redundant.html b/accessibility-checker-engine/help-v4/en-US/img_alt_redundant.html
index 8846cba75..85ca25a99 100644
--- a/accessibility-checker-engine/help-v4/en-US/img_alt_redundant.html
+++ b/accessibility-checker-engine/help-v4/en-US/img_alt_redundant.html
@@ -54,7 +54,7 @@ <h3 id="ruleMessage"></h3>
 
 * If a link has text and a redundant image, set the image `alt` attribute to `alt=“”` (null alt without any spaces);
 * **Or**, if a link has text and an image that adds important information to the text, set the image `alt` attribute to convey the added information.
-  (e.g. `<a><img alt="urgent">new mail</a>`);
+  (e.g., `<a><img alt="urgent">new mail</a>`);
 * **Or**, if adjacent links have different targets but the same text, change the link text or the `alt` attribute on the image to distinguish the purpose of each link;
 * **Or**, if adjacent links have the same target, combine them into a single link and set the image `alt` attribute to `alt=“”`.
 
diff --git a/accessibility-checker-engine/help-v4/en-US/input_checkboxes_grouped.html b/accessibility-checker-engine/help-v4/en-US/input_checkboxes_grouped.html
index d72ed1080..e447617ff 100644
--- a/accessibility-checker-engine/help-v4/en-US/input_checkboxes_grouped.html
+++ b/accessibility-checker-engine/help-v4/en-US/input_checkboxes_grouped.html
@@ -45,7 +45,7 @@ <h3 id="ruleMessage"></h3>
 
 ### Why is this important?
 
-Grouping related radio buttons and checkboxes enables assistive technology to convey the group relationship to users (e.g. "group of 5 radio buttons").
+Grouping related radio buttons and checkboxes enables assistive technology to convey the group relationship to users (e.g., "group of 5 radio buttons").
 
 <!-- This is where the code snippet is injected -->
 <div id="locSnippet"></div>
diff --git a/accessibility-checker-engine/help-v4/en-US/input_label_exists.html b/accessibility-checker-engine/help-v4/en-US/input_label_exists.html
index fc6ab0106..c4bc6405f 100644
--- a/accessibility-checker-engine/help-v4/en-US/input_label_exists.html
+++ b/accessibility-checker-engine/help-v4/en-US/input_label_exists.html
@@ -52,10 +52,10 @@ <h3 id="ruleMessage"></h3>
 
 ### What to do
 
-* If the control is a [labelable](https://html.spec.whatwg.org/multipage/forms.html#category-label) element, add a `for` attribute to a visible label with the `id` of this control (e.g. `<label for="controlID">`);
+* If the control is a [labelable](https://html.spec.whatwg.org/multipage/forms.html#category-label) element, add a `for` attribute to a visible label with the `id` of this control (e.g., `<label for="controlID">`);
 * **Or**, if the  control is a labelable element, put the control inside a visible `<label>` element;
 * **Or**, add an `aria-labelledby` attribute to the control. It must point to visible text on the page that is meaningful as a label;
-* **Or**, if the design cannot have a visible label, provide a label using the `aria-label` attribute (e.g. `aria-label="Activities"`);
+* **Or**, if the design cannot have a visible label, provide a label using the `aria-label` attribute (e.g., `aria-label="Activities"`);
 * **Or**, if the design cannot have a visible label, use the `title` attribute to provide a label.
 
 </script></mark-down>
diff --git a/accessibility-checker-engine/help-v4/en-US/list_markup_review.html b/accessibility-checker-engine/help-v4/en-US/list_markup_review.html
index 48387b9f8..e050f28f5 100644
--- a/accessibility-checker-engine/help-v4/en-US/list_markup_review.html
+++ b/accessibility-checker-engine/help-v4/en-US/list_markup_review.html
@@ -53,7 +53,7 @@ <h3 id="ruleMessage"></h3>
 ### What to do
 
  * Verify that the content is not a list;
- * **Or**, if this is a list, use HTML list elements (e.g. `<ol>`, `<ul>`, `<li>`) to create the list and CSS to style the list as desired.
+ * **Or**, if this is a list, use HTML list elements (e.g., `<ol>`, `<ul>`, `<li>`) to create the list and CSS to style the list as desired.
 
 </script></mark-down>
 <!-- End main panel -->
diff --git a/accessibility-checker-engine/help-v4/en-US/meta_refresh_delay.html b/accessibility-checker-engine/help-v4/en-US/meta_refresh_delay.html
index 01830dff1..9f182d47a 100644
--- a/accessibility-checker-engine/help-v4/en-US/meta_refresh_delay.html
+++ b/accessibility-checker-engine/help-v4/en-US/meta_refresh_delay.html
@@ -52,7 +52,7 @@ <h3 id="ruleMessage"></h3>
 
 ### What to do
 
- * Remove the `<META>` tag that causes an automatic page refresh (e.g. `<META HTTP-EQUIV="Refresh" CONTENT="10">`) and use a different method to update information on the page;
+ * Remove the `<META>` tag that causes an automatic page refresh (e.g., `<META HTTP-EQUIV="Refresh" CONTENT="10">`) and use a different method to update information on the page;
  * **Or**, provide an option to turn off, extend, or adjust the timing of the page refresh;
  * **Or**, at the top of the page, provide a single line of explanation and link to a non-refreshing page. For example "This page automatically reloads every 10 seconds. A `<a href="..."> non-updating equivalent page </a>` with a refresh button is available."
 
diff --git a/accessibility-checker-engine/help-v4/en-US/skip_main_described.html b/accessibility-checker-engine/help-v4/en-US/skip_main_described.html
index 462a5861e..15e587e66 100644
--- a/accessibility-checker-engine/help-v4/en-US/skip_main_described.html
+++ b/accessibility-checker-engine/help-v4/en-US/skip_main_described.html
@@ -52,7 +52,7 @@ <h3 id="ruleMessage"></h3>
 
 ### What to do
 
- * If this link skips content on the page, verify the link text communicates where it skips to (e.g. "Jump to site navigation");
+ * If this link skips content on the page, verify the link text communicates where it skips to (e.g., "Jump to site navigation");
  * **Or**, if this link goes to the main content on the page, set the link text to "Skip to main content".
 
 For example:
diff --git a/accessibility-checker-engine/help-v4/en-US/style_background_decorative.html b/accessibility-checker-engine/help-v4/en-US/style_background_decorative.html
index f0b313c5d..b5df8e4c8 100644
--- a/accessibility-checker-engine/help-v4/en-US/style_background_decorative.html
+++ b/accessibility-checker-engine/help-v4/en-US/style_background_decorative.html
@@ -54,7 +54,7 @@ <h3 id="ruleMessage"></h3>
 
 * If the background image contains important text, use real text rather than an image of text;
 * **Or**, if the background image conveys important information, use the `<img>` element with an `"alt"` attribute instead of a background image;
-* **Or**, provide a text alternative for the information that shows if the CSS image is not displayed (e.g. for users using alternate backgrounds and users using high contrast mode).
+* **Or**, provide a text alternative for the information that shows if the CSS image is not displayed (e.g., for users using alternate backgrounds and users using high contrast mode).
 
 </script></mark-down>
 <!-- End main panel -->
diff --git a/accessibility-checker-engine/help-v4/en-US/style_color_misuse.html b/accessibility-checker-engine/help-v4/en-US/style_color_misuse.html
index 5474667b6..c6b58b32c 100644
--- a/accessibility-checker-engine/help-v4/en-US/style_color_misuse.html
+++ b/accessibility-checker-engine/help-v4/en-US/style_color_misuse.html
@@ -52,8 +52,8 @@ <h3 id="ruleMessage"></h3>
 
 ### What to do
 
-* If color is used to indicate required fields, also use an asterisk ('*') to visually indicate required fields without color (e.g.  “required fields are red and indicated with '*' ") and indicate them programmatically with the `required` attribute;
-* **Or**, if use of color conveys other meaning or information, check that there is another visual indicator together with programmatic or text information that conveys the same information (e.g. use “green checkmarks” and “red crosses” instead of just “red” and “green” indicators).
+* If color is used to indicate required fields, also use an asterisk ('*') to visually indicate required fields without color (e.g.,  “required fields are red and indicated with '*' ") and indicate them programmatically with the `required` attribute;
+* **Or**, if use of color conveys other meaning or information, check that there is another visual indicator together with programmatic or text information that conveys the same information (e.g., use “green checkmarks” and “red crosses” instead of just “red” and “green” indicators).
 
 </script></mark-down>
 <!-- End main panel -->
diff --git a/accessibility-checker-engine/help-v4/en-US/table_headers_exists.html b/accessibility-checker-engine/help-v4/en-US/table_headers_exists.html
index 9d70636da..62693da05 100644
--- a/accessibility-checker-engine/help-v4/en-US/table_headers_exists.html
+++ b/accessibility-checker-engine/help-v4/en-US/table_headers_exists.html
@@ -56,7 +56,7 @@ <h3 id="ruleMessage"></h3>
  * **Or**, identify the table as layout with `role="presentation"`  or `role="none"`;
  * **Or**, if this is a simple data table, use the `<th>` element to identify headers in the first row;
  * **Or**, if this is complex data table, add the `scope` attribute to the `<th>` element to identify headers and define the scope of the header for each data cell;
- * **Or**, if this is a complex table with multiple rows or columns as headers, use the `id` attribute with the `<th>` element and the `headers` attribute with the `<td>` element to identify multiple headers for each data cell (e.g. `<td headers="h1 h2">`).
+ * **Or**, if this is a complex table with multiple rows or columns as headers, use the `id` attribute with the `<th>` element and the `headers` attribute with the `<td>` element to identify multiple headers for each data cell (e.g., `<td headers="h1 h2">`).
 
 </script></mark-down>
 <!-- End main panel -->
diff --git a/accessibility-checker-engine/help-v4/en-US/table_headers_related.html b/accessibility-checker-engine/help-v4/en-US/table_headers_related.html
index cfdf41c8c..3a54d5092 100644
--- a/accessibility-checker-engine/help-v4/en-US/table_headers_related.html
+++ b/accessibility-checker-engine/help-v4/en-US/table_headers_related.html
@@ -54,8 +54,8 @@ <h3 id="ruleMessage"></h3>
 
  * If this is not a data table (no relational data), use CSS instead of a `<table>` element to lay out your content (highly recommended); 
  * **Or**, identify the table as layout with `role="presentation"`  or `role="none"`;
- * **Or**, use the `id` attribute to provide an identifier for header cells (e.g. `<th id="school">`);
- * **And**, use the `header` attribute on data cells to identify the appropriate header cells (e.g. `<td headers="school teacher grade">`).
+ * **Or**, use the `id` attribute to provide an identifier for header cells (e.g., `<th id="school">`);
+ * **And**, use the `header` attribute on data cells to identify the appropriate header cells (e.g., `<td headers="school teacher grade">`).
 
 </script></mark-down>
 <!-- End main panel -->
diff --git a/accessibility-checker-engine/help-v4/en-US/text_block_heading.html b/accessibility-checker-engine/help-v4/en-US/text_block_heading.html
index 516b5751d..4df4f9b31 100644
--- a/accessibility-checker-engine/help-v4/en-US/text_block_heading.html
+++ b/accessibility-checker-engine/help-v4/en-US/text_block_heading.html
@@ -52,7 +52,7 @@ <h3 id="ruleMessage"></h3>
 
 ### What to do
 
- * If this text is intended to be a heading, use the `<h>` elements (h1-h6) rather than style alone to define heading text (e.g. `<h2>Section 1</h2>`);
+ * If this text is intended to be a heading, use the `<h>` elements (h1-h6) rather than style alone to define heading text (e.g., `<h2>Section 1</h2>`);
  * **Or**, use other markup so the element's semantic meaning is exposed to assistive technology that is appropriate for the content of the element.
 
 </script></mark-down>
diff --git a/accessibility-checker-engine/help-v4/en-US/text_sensory_misuse.html b/accessibility-checker-engine/help-v4/en-US/text_sensory_misuse.html
index cd1af25b2..4155d2896 100644
--- a/accessibility-checker-engine/help-v4/en-US/text_sensory_misuse.html
+++ b/accessibility-checker-engine/help-v4/en-US/text_sensory_misuse.html
@@ -45,15 +45,15 @@ <h3 id="ruleMessage"></h3>
 
 ### Why is this important?
 
-Instructions that use shape or location to describe elements (e.g. “select the button on the right”) can help many users understand content. However, sensory characteristics should not be the only means of conveying information when giving instructions. It is not meaningful to users who cannot see the object or the page layout. Adding a label to clarify sensory language will allow all users to better understand the instructions.
+Instructions that use shape or location to describe elements (e.g., “select the button on the right”) can help many users understand content. However, sensory characteristics should not be the only means of conveying information when giving instructions. It is not meaningful to users who cannot see the object or the page layout. Adding a label to clarify sensory language will allow all users to better understand the instructions.
 
 <!-- This is where the code snippet is injected -->
 <div id="locSnippet"></div>
 
 ### What to do
 
-* If this word is used in instructions to reference a page element or area, make sure there is also a visible text label for the element or area referenced in the instructions (e.g. "the ‘Delete’ button on the right");
-* **Or**, if the word if not used in instructions, or does not convey sensory meaning (e.g. "the moon above the clouds"), no action is needed.
+* If this word is used in instructions to reference a page element or area, make sure there is also a visible text label for the element or area referenced in the instructions (e.g., "the ‘Delete’ button on the right");
+* **Or**, if the word if not used in instructions, or does not convey sensory meaning (e.g., "the moon above the clouds"), no action is needed.
 
 </script></mark-down>
 <!-- End main panel -->
diff --git a/accessibility-checker-engine/help-v4/en-US/text_spacing_valid.html b/accessibility-checker-engine/help-v4/en-US/text_spacing_valid.html
index d9de623cc..b0e94b894 100644
--- a/accessibility-checker-engine/help-v4/en-US/text_spacing_valid.html
+++ b/accessibility-checker-engine/help-v4/en-US/text_spacing_valid.html
@@ -46,7 +46,7 @@ <h3 id="ruleMessage"></h3>
 ### Why is this important?
 
 End users need to be able to adjust text, word, and line spacing to make it easier to read.
-And when users make adjustments the content needs to still be fully usable and understandable (e.g. no truncation).
+And when users make adjustments the content needs to still be fully usable and understandable (e.g., no truncation).
 Assistive technologies cannot adjust spacing when authors use the CSS `!important` attribute.
 
 Authors must ensure the content can be transformed (such as through user style sheets) to attain all of the following specific requirements without loss of content or functionality:
diff --git a/accessibility-checker-engine/src/v2/aria/NameComputation.md b/accessibility-checker-engine/src/v2/aria/NameComputation.md
index db1401593..dbbac8788 100644
--- a/accessibility-checker-engine/src/v2/aria/NameComputation.md
+++ b/accessibility-checker-engine/src/v2/aria/NameComputation.md
@@ -13,8 +13,8 @@ The text alternative for a given element is computed as follows:
 3. if the current node has an aria-label attribute whose value is not the empty string, nor, when trimmed of white space, is not the empty string:
     * If traversal of the current node is due to recursion and the current node is an embedded control as defined in step 2E, ignore aria-label and skip to rule 2E.
     * Otherwise, return the value of aria-label.
-4. Otherwise, if the current node's native markup provides an attribute (e.g. title) or element (e.g. HTML label) that defines a text alternative, return that alternative in the form of a flat string as defined by the host language, unless the element is marked as presentational (role="presentation"or role="none").
-5. **[walk || aria-labelledby]** Otherwise, if the current node is a control embedded within the label (e.g. the label element in HTMLor any element directly referenced by aria-labelledby) for another widget, where the user can adjust the embedded control's value, then include the embedded control as part of the text alternative in the following manner:
+4. Otherwise, if the current node's native markup provides an attribute (e.g., title) or element (e.g., HTML label) that defines a text alternative, return that alternative in the form of a flat string as defined by the host language, unless the element is marked as presentational (role="presentation"or role="none").
+5. **[walk || aria-labelledby]** Otherwise, if the current node is a control embedded within the label (e.g., the label element in HTMLor any element directly referenced by aria-labelledby) for another widget, where the user can adjust the embedded control's value, then include the embedded control as part of the text alternative in the following manner:
     * If the embedded control has role textbox, return its value.
     * If the embedded control has role menu button, return the text alternative of the button.
     * If the embedded control has role combobox or listbox, return the text alternative of the chosen option.
@@ -22,7 +22,7 @@ The text alternative for a given element is computed as follows:
         * If the aria-valuetext property is present, return its value,
         * Otherwise, if the aria-valuenow property is present, return its value,
         * Otherwise, use the value as specified by a host language attribute.
-6. Otherwise, if the current node's role allows name from content, or if the current node is referenced by aria-labelledby, aria-describedby, or is a native host language text alternative element (e.g. label in HTML), or is a descendant of a native host language text alternative element:
+6. Otherwise, if the current node's role allows name from content, or if the current node is referenced by aria-labelledby, aria-describedby, or is a native host language text alternative element (e.g., label in HTML), or is a descendant of a native host language text alternative element:
     1. Set the accumulated text to the empty string.
     2. Check for CSS generated textual content associated with the current node and include it in the accumulated text. The CSS :before and :after pseudo elements [CSS2] can provide textual content for elements that have a content model.
         * For :before pseudo elements, User agents MUST prepend CSS textual content, without a space, to the textual content of the current node.
diff --git a/accessibility-checker-engine/src/v4/rules/aria_graphic_labelled.ts b/accessibility-checker-engine/src/v4/rules/aria_graphic_labelled.ts
index f15d8d3a0..2e88182be 100644
--- a/accessibility-checker-engine/src/v4/rules/aria_graphic_labelled.ts
+++ b/accessibility-checker-engine/src/v4/rules/aria_graphic_labelled.ts
@@ -73,7 +73,7 @@ export let aria_graphic_labelled: Rule = {
         }*/
 
         // If role === img, you must use an aria label
-        //check attributes aria-label and aria-labelledby for other tags (e.g. <div>, <span>, etc)
+        //check attributes aria-label and aria-labelledby for other tags (e.g., <div>, <span>, etc)
         let passed = RPTUtil.getAriaLabel(ruleContext).length > 0;
 
         if (!passed && ruleContext.nodeName.toLowerCase() === "svg") {
diff --git a/accessibility-checker-engine/src/v4/rules/aria_img_labelled.ts b/accessibility-checker-engine/src/v4/rules/aria_img_labelled.ts
index cf3736ac6..80b586a64 100644
--- a/accessibility-checker-engine/src/v4/rules/aria_img_labelled.ts
+++ b/accessibility-checker-engine/src/v4/rules/aria_img_labelled.ts
@@ -79,7 +79,7 @@ export let aria_img_labelled: Rule = {
          */
         
         // If role === img, you must use an aria label
-        //check attributes aria-label and aria-labelledby for other tags (e.g. <div>, <span>, etc)
+        //check attributes aria-label and aria-labelledby for other tags (e.g., <div>, <span>, etc)
         let passed = RPTUtil.getAriaLabel(ruleContext).length > 0;
 
         if (!passed && ruleContext.nodeName.toLowerCase() === "svg") {
diff --git a/accessibility-checker-engine/src/v4/rules/aria_landmark_name_unique.ts b/accessibility-checker-engine/src/v4/rules/aria_landmark_name_unique.ts
index 1022a5b8c..211ef401b 100644
--- a/accessibility-checker-engine/src/v4/rules/aria_landmark_name_unique.ts
+++ b/accessibility-checker-engine/src/v4/rules/aria_landmark_name_unique.ts
@@ -151,7 +151,7 @@ export let aria_landmark_name_unique: Rule = {
                             "navigation",
                             "region",
                             "search",
-                        ].includes(els[j].getAttribute("role")); // TODO we are not covering the case where a elemenent with multiple roles. E.g. role = "form banner". This is a improvment we might want to add in the future.
+                        ].includes(els[j].getAttribute("role")); // TODO we are not covering the case where a elemenent with multiple roles. e.g., role = "form banner". This is a improvment we might want to add in the future.
                     }
                     if (tagNameTrigger || roleNameTrigger) {
                         // Nearest parent-landmark found
diff --git a/accessibility-checker-engine/src/v4/rules/element_accesskey_labelled.ts b/accessibility-checker-engine/src/v4/rules/element_accesskey_labelled.ts
index 0481b054d..95d9644a0 100644
--- a/accessibility-checker-engine/src/v4/rules/element_accesskey_labelled.ts
+++ b/accessibility-checker-engine/src/v4/rules/element_accesskey_labelled.ts
@@ -59,7 +59,7 @@ export let element_accesskey_labelled: Rule = {
             passed = true;
         } else if (ruleContext.nodeName.toLowerCase() === "input"
             && DOMWalker.parentNode(ruleContext).nodeName.toLowerCase() === "label") {
-            // assume the validity of the label, e.g. empty label, is checked by a different rule
+            // assume the validity of the label, e.g., empty label, is checked by a different rule
             passed = true;
         }
 
diff --git a/accessibility-checker-engine/src/v4/rules/label_name_visible.ts b/accessibility-checker-engine/src/v4/rules/label_name_visible.ts
index c37e1bfe7..8cd9a546c 100644
--- a/accessibility-checker-engine/src/v4/rules/label_name_visible.ts
+++ b/accessibility-checker-engine/src/v4/rules/label_name_visible.ts
@@ -166,10 +166,10 @@ export let label_name_visible: Rule = {
             theLabel = theLabel.replace(nonalphanumeric, " "); // only consider alphanumeric characters
             let normalizedLabel = RPTUtil.normalizeSpacing(theLabel).toLowerCase();
 
-            if (normalizedText.length > 1) { // skip non-text content. e.g. <button aria-label="close">X</button>
+            if (normalizedText.length > 1) { // skip non-text content. e.g., <button aria-label="close">X</button>
                 let location = normalizedLabel.indexOf(normalizedText);
 
-                // Avoid matching partial words.e.g. text "name" should not match 'surname' or 'names'
+                // Avoid matching partial words.e.g., text "name" should not match 'surname' or 'names'
                 if (location >= 0 && normalizedLabel.length > normalizedText.length) {
                     let letters = /^[0-9a-zA-Z]+$/;
                     if ((location + normalizedText.length) < normalizedLabel.length) {
diff --git a/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_active_descendant_ruleunit/w3c_example1_collapsed.html b/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_active_descendant_ruleunit/w3c_example1_collapsed.html
index 936c577d3..46dfe3be0 100644
--- a/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_active_descendant_ruleunit/w3c_example1_collapsed.html
+++ b/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_active_descendant_ruleunit/w3c_example1_collapsed.html
@@ -26,7 +26,7 @@
                     aria-labelledby="combo1-label"
                     tabindex="-1">
                 <!-- options are inserted here -->
-                <!-- e.g. <div role="option" id="op1">option text</div>  -->
+                <!-- e.g., <div role="option" id="op1">option text</div>  -->
                 </div>
             </div>
         </main>
diff --git a/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_autocomplete_valid_ruleunit/w3c_example1_collapsed.html b/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_autocomplete_valid_ruleunit/w3c_example1_collapsed.html
index 02a5a9d3a..5f481538a 100644
--- a/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_autocomplete_valid_ruleunit/w3c_example1_collapsed.html
+++ b/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_autocomplete_valid_ruleunit/w3c_example1_collapsed.html
@@ -26,7 +26,7 @@
                     aria-labelledby="combo1-label"
                     tabindex="-1">
                 <!-- options are inserted here -->
-                <!-- e.g. <div role="option" id="op1">option text</div>  -->
+                <!-- e.g., <div role="option" id="op1">option text</div>  -->
                 </div>
             </div>
         </main>
diff --git a/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_design_valid_ruleunit/w3c_example1_collapsed.html b/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_design_valid_ruleunit/w3c_example1_collapsed.html
index 08f060dac..a35b6b9c8 100644
--- a/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_design_valid_ruleunit/w3c_example1_collapsed.html
+++ b/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_design_valid_ruleunit/w3c_example1_collapsed.html
@@ -26,7 +26,7 @@
                     aria-labelledby="combo1-label"
                     tabindex="-1">
                 <!-- options are inserted here -->
-                <!-- e.g. <div role="option" id="op1">option text</div>  -->
+                <!-- e.g., <div role="option" id="op1">option text</div>  -->
                 </div>
             </div>
         </main>
diff --git a/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_focusable_elements_ruleunit/w3c_example1_collapsed.html b/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_focusable_elements_ruleunit/w3c_example1_collapsed.html
index d6920a70e..cb1431822 100644
--- a/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_focusable_elements_ruleunit/w3c_example1_collapsed.html
+++ b/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_focusable_elements_ruleunit/w3c_example1_collapsed.html
@@ -26,7 +26,7 @@
                     aria-labelledby="combo1-label"
                     tabindex="-1">
                 <!-- options are inserted here -->
-                <!-- e.g. <div role="option" id="op1">option text</div>  -->
+                <!-- e.g., <div role="option" id="op1">option text</div>  -->
                 </div>
             </div>
         </main>
diff --git a/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_haspopup_valid_ruleunit/w3c_example1_collapsed.html b/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_haspopup_valid_ruleunit/w3c_example1_collapsed.html
index 3ec003118..f5cfebec6 100644
--- a/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_haspopup_valid_ruleunit/w3c_example1_collapsed.html
+++ b/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_haspopup_valid_ruleunit/w3c_example1_collapsed.html
@@ -26,7 +26,7 @@
                     aria-labelledby="combo1-label"
                     tabindex="-1">
                 <!-- options are inserted here -->
-                <!-- e.g. <div role="option" id="op1">option text</div>  -->
+                <!-- e.g., <div role="option" id="op1">option text</div>  -->
                 </div>
             </div>
         </main>
diff --git a/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_popup_reference_ruleunit/w3c_example1_collapsed.html b/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_popup_reference_ruleunit/w3c_example1_collapsed.html
index 808f3b4fe..2f9994445 100644
--- a/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_popup_reference_ruleunit/w3c_example1_collapsed.html
+++ b/accessibility-checker-engine/test/v2/checker/accessibility/rules/combobox_popup_reference_ruleunit/w3c_example1_collapsed.html
@@ -26,7 +26,7 @@
                     aria-labelledby="combo1-label"
                     tabindex="-1">
                 <!-- options are inserted here -->
-                <!-- e.g. <div role="option" id="op1">option text</div>  -->
+                <!-- e.g., <div role="option" id="op1">option text</div>  -->
                 </div>
             </div>
         </main>
diff --git a/accessibility-checker-extension/src/ts/docs/UsingACApp.tsx b/accessibility-checker-extension/src/ts/docs/UsingACApp.tsx
index aa2e78d23..8555e9094 100644
--- a/accessibility-checker-extension/src/ts/docs/UsingACApp.tsx
+++ b/accessibility-checker-extension/src/ts/docs/UsingACApp.tsx
@@ -334,7 +334,7 @@ class UsingACApp extends React.Component<{}, UsingACAppState> {
                 </p>
                 <OrderedList>
                     <ListItem>Select an element in the DOM, or use the ‘Inspect element’ command on page.</ListItem>
-                    <ListItem>Select element name in focus view (e.g. &lt;html&gt;) to view related issues</ListItem>
+                    <ListItem>Select element name in focus view (e.g., &lt;html&gt;) to view related issues</ListItem>
                     <ListItem>Select ‘All’ in the focus view to see all issues again</ListItem>
                 </OrderedList>
                 <h3 id="keyboard_checker_mode">3.5. Keyboard checker mode</h3>
diff --git a/accessibility-checker/README.md b/accessibility-checker/README.md
index ec7094f0c..21d8a26f7 100644
--- a/accessibility-checker/README.md
+++ b/accessibility-checker/README.md
@@ -21,7 +21,7 @@ To get started using the deployed packages, review [Node accessibility-checker](
 This module provides some basic command-line utilities that will allow scanning files, directories, and URLs:
 
 - Create a .txt file with path(s) to files, directories, or a list of URLs to be scanned
-- Provide the `npx achecker` the full path of the .txt file to start the scan (e.g. `npx achecker path/to/your/file.txt`)
+- Provide the `npx achecker` the full path of the .txt file to start the scan (e.g., `npx achecker path/to/your/file.txt`)
 - Run `npx achecker`
 
 Review the [accessibility-checker/src/README](src/README.md) for more information.
diff --git a/accessibility-checker/src/README.md b/accessibility-checker/src/README.md
index 8c339c2ff..66215957b 100644
--- a/accessibility-checker/src/README.md
+++ b/accessibility-checker/src/README.md
@@ -18,7 +18,7 @@ Note that we have seen some non-standard CSS parsing with Zombie, so be aware of
 This module provides some basic command-line utilities that will allow scanning files, directories, and URLs:
 
 - Create a .txt file with path(s) to files, directories, or a list of URLs to be scanned
-- Provide the `npx achecker` the full path of the .txt file to start the scan (e.g. `npx achecker path/to/your/file.txt`)
+- Provide the `npx achecker` the full path of the .txt file to start the scan (e.g., `npx achecker path/to/your/file.txt`)
 - Run `npx achecker`
 
 ### Programmatic
diff --git a/cypress-accessibility-checker/cypress/plugins/index.js b/cypress-accessibility-checker/cypress/plugins/index.js
index 59b2bab6e..bc5b4151d 100644
--- a/cypress-accessibility-checker/cypress/plugins/index.js
+++ b/cypress-accessibility-checker/cypress/plugins/index.js
@@ -9,7 +9,7 @@
 // https://on.cypress.io/plugins-guide
 // ***********************************************************
 
-// This function is called when a project is opened or re-opened (e.g. due to
+// This function is called when a project is opened or re-opened (e.g., due to
 // the project's config changing)
 
 /**