Update notes on 2.5.8 in SC problematic for closed functionality

Per WCAG2ICT TF decision on 1 Feb.

success-criteria-problematic-for-closed-functionality.md

@@ -41,8 +41,8 @@ There are Success Criteria that can be problematic for developers of closed func
 <li><a href="#pointer-cancellation">2.5.2 Pointer Cancellation</a>—As noted in the section <a href="#applying-sc-2-5-2-pointer-cancellation-to-non-web-documents-and-software">Applying SC 2.5.2 Pointer Cancellation to Non-Web Documents and Software</a>, examples of 'essential' functionality are features for meeting environmental energy usage requirements (like waking a device from sleep, power saver mode, and low power state).</li>  
 <li><a href="#label-in-name">2.5.3 Label in Name</a>—Requires information in a programmatically determinable form; specifically, the programmatic name contains the text of the visual label.</li>
 <li><a href="#target-size-minimum">2.5.8 Target Size (Minimum)</a>—2.5.8 Target Size (Minimum) - This Success Criterion uses CSS pixels for defining the target size. Closed functionality may not use CSS pixels as a standard measurement, but the definition of 'CSS pixel' still applies as described in <a href="#applying-css-pixel-to-non-web-documents-and-software">Applying “CSS pixel” to Non-Web Documents and Software</a>. If the system supports a density-independent pixel measurement, it should be used in place of CSS pixels.
-<div class="note">If the viewing distance or pixel density of the system is unknown, approximating the reference pixel as described in Applying “CSS pixel” to Non-Web Documents and Software is not possible.</div>
-<div class="note">For software designed to run on specific known hardware, a physical size standard would be more straightforward to apply, as calculations for CSS pixels is dependent on the viewing distance and pixel density of the display.</div></li>
+<div class="note">If the viewing distance and pixel density of the system are unknown, approximating the reference pixel as described in Applying “CSS pixel” to Non-Web Documents and Software is not possible.</div>
+<div class="note">For software designed to run on specific known hardware, a physical size standard would be more straightforward to apply, as calculations for a CSS pixel are dependent on the viewing distance or pixel density of the display.</div></li>
 <li><a href="#language-of-page">3.1.1 Language of Page</a>—Requires language information in a programmatically determinable form intended to drive correct pronunciation. Where another mechanism achieves correct pronunciation for closed functionality, such as self-voicing, the intent of this success criterion would be met.</li>
 <li><a href="#language-of-parts">3.1.2 Language of Parts</a>—Requires language information in a programmatically determinable form intended to drive correct pronunciation. Where another mechanism achieves correct pronunciation for closed functionality, such as self-voicing, the intent of this success criterion would be met.</li>
 <li><a href="#error-identification">3.3.1 Error Identification</a>—while it's important for errors that can be detected to be described to the user, for closed functionality, the error description doesn't have to be provided in text, as defined in WCAG 2;</li>