add repair caveat

index.html

@@ -7658,11 +7658,11 @@ <h5>Presentational Role Inheritance</h5>
 				    <li>If <code>aria-valuemin</code> is missing or not a <a href="#valuetype_number">number</a>, it defaults to 0 (zero). </li>
 				    <li>If <code>aria-valuemax</code> is missing or not a <a href="#valuetype_number">number</a>, it defaults to 100. </li>
 				</ul>
-				<p>Authors MUST set either the <pref>aria-valuenow</pref> attribute, the <pref>aria-valuetext</pref> attribute, or both. If both the <code>aria-valuenow</code> and <code>aria-valuetext</code> attriburtes are missing or  <code>aria-valuenow</code> has an unexpected value, browsers MAY implement the repair techniques specified in the <a href="#authorErrorDefaultValuesTable">section describing handling author errors in states and properties</a>, which are equivalent to the repair techniques for <code>&lt;input type="[^input/type/range^]"&gt;</code> in HTML.</p>
+				<p>Authors MUST set either the <pref>aria-valuenow</pref> attribute, the <pref>aria-valuetext</pref> attribute, or both. If both the <code>aria-valuenow</code> and <code>aria-valuetext</code> attributes are missing or <code>aria-valuenow</code> has an unexpected value, <a>user agents</a> MAY implement the repair techniques specified in the <a href="#authorErrorDefaultValuesTable">section describing handling author errors in states and properties</a>, which are equivalent to the repair techniques for <code>&lt;input type="[^input/type/range^]"&gt;</code> in HTML. However, both <a>user agents</a> and <a>assistive technologies</a> SHOULD NOT expose a fallback value for <code>aria-valuenow</code> if the author has only specified the <code>aria-valuetext</code> attribute.</p>
 				<p>Elements with the role <code>slider</code> have an implicit <pref>aria-orientation</pref> value of <code>horizontal</code>.</p>
 				<div class="note">
 					<p>It is usually advisable for a slider to express its current value as a parsable <a href="#valuetype_number">number</a> using <pref>aria-valuenow</pref>. However, there are use cases where <pref>aria-valuetext</pref> alone provides a superior user experience.</p>
-					<p>For example, pain can be measured along a range of values in which each value is most helpfully expressed by descriptive text rather than superficially expressed by an unintuitive number.</p>
+					<p>For example, pain can be measured along a range of values in which each value is most helpfully expressed by descriptive text rather than an unintuitive number.</p>
 				</div>
 				<pre class="example highlight">
 &lt;!-- Warning: this code example is incomplete. --&gt;