Editorial review of 5

SHA: 8f39bae
Reason: push, by jasonjgw

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

Author: jenstrickland

index.html

@@ -437,11 +437,11 @@ <h1 id="title" class="title">Collaboration Tools Accessibility User Requirements
       <p>Collaboration tools may send notifications to the user for a variety of reasons. For example, a user may be notified if a collaborator asynchronously submits changes to a document or project, or adds a comment. These notifications may be delivered via operating system facilities, or by a messaging service, such as e-mail or an instant message protocol. Moreover, the collaboration tool may support commenting, issue tracking, or other forms of interaction via external messaging. These optional capabilities are addressed in the following user needs and system requirements.</p>
       <ul>
         <li><strong>User Need 15:</strong> Users who are easily distracted or overwhelmed need to receive only notifications that are crucially important to their collaborative activity.</li>
-        <li><strong>REQ 15:</strong> Ensure that users can choose which types of notification are delivered, and which are suppressed, according to the nature of the information conveyed.</li>
+        <li><strong>REQ 15:</strong> Ensure that users can choose which types of notifications are delivered, and which are suppressed, according to the nature of the information conveyed.</li>
         <li><strong>User Need 16:</strong> Users for whom reading text is slow or difficult need information that is important to the task at hand to be clearly distinguished and prioritized.</li>
-        <li><strong>REQ 16A:</strong> Provide a mode of operation in which notifications are short, and links to more detailed information are included. In this mode, full details are not provided in the notification. For example, a user could be notified that a comment or issue has been created,  with the full text being available only via a link rather than as part of the notificational message itself.</li>
-        <li><strong>REQ 16B:</strong> If e-mail or a similar medium is used to deliver notifications, ensure that the <em>subject</em> of the message clearly specifies the project, document or issue title relevant to the notification.</li>
-        <li><strong>REQ 16C:</strong> If multiple notifications are provided together (e.g., in a single message), ensure that the user can sort the notifications according to reasonable preferences, for example, most recent first, or oldest first. This is applicable, for example, to a series of comments organized as <q>threads</q> of discussion, all delivered in a single summary message to the user.</li>
+        <li><strong>REQ 16A:</strong> Provide a mode of operation in which notifications are short, and links to more detailed information are included. In this mode, full details are not provided in the notification. For example, a user could be notified that a comment or issue has been created,  with the full text being available only via a link rather than as part of the notification message itself.</li>
+        <li><strong>REQ 16B:</strong> If e-mail or a similar medium is used to deliver notifications, ensure that the <em>subject</em> of the message clearly specifies the project, document, or issue title relevant to the notification.</li>
+        <li><strong>REQ 16C:</strong> If multiple notifications are provided together (e.g., in a single message), ensure that the user can sort the notifications according to reasonable preferences, for example, most recent first or oldest first. This is applicable, for example, to a series of comments organized as <q>threads</q> of discussion, all delivered in a single summary message to the user.</li>
       </ul>
     </section>
     <section id="access-control"><div class="header-wrapper"><h2 id="x6-access-controls"><bdi class="secno">6. </bdi>Access Controls</h2><a class="self-link" href="#access-control" aria-label="Permalink for Section 6."></a></div>