Change UI-EVENTS reference to UIEVENTS

seems we accidentally used both variant names for the same reference

index.html

@@ -407,7 +407,7 @@ <h2>Firing events using the <code>PointerEvent</code> interface</h2>
 
                 <p>Fire the event to the determined target. The user agent SHOULD treat the target as if the pointing device has moved over it for the purpose of <a href="uievents/#events-mouseevent-event-order">ensuring event ordering</a>.
 
-                <div class="note">Using the <a>pointer capture target override</a> as the target instead of the normal hit-test result may fire some boundary events, as defined by [[UI-EVENTS]]. This is the same as the pointer leaving its previous target and entering this new capturing target. When the capture is released, the same scenario may happen, as the pointer is leaving the capturing target and entering the hit-test target.</div>
+                <div class="note">Using the <a>pointer capture target override</a> as the target instead of the normal hit-test result may fire some boundary events, as defined by [[UIEVENTS]]. This is the same as the pointer leaving its previous target and entering this new capturing target. When the capture is released, the same scenario may happen, as the pointer is leaving the capturing target and entering the hit-test target.</div>
 
                 <section>
                   <h3>Attributes and default actions</h3>
@@ -1423,10 +1423,10 @@ <h1>Glossary</h1>
                 <dd><p>Measurable properties represent values relating to continuous pointer sensor data that is expressed using a real number or an
                     integer from a large domain. For pointer events, <code>width</code>, <code>height</code>, <code>pressure</code>,
                     <code>tangentialPressure</code>, <code>tiltX</code>, <code>tiltY</code>, <code>twist</code>,
-                    <code>altitudeAngle</code>, <code>azimuthAngle</code>, and the [[UI-EVENTS]] Mouse Event model properties
+                    <code>altitudeAngle</code>, <code>azimuthAngle</code>, and the [[UIEVENTS]] Mouse Event model properties
                     <code>screenX</code>, <code>screenY</code>, <code>clientX</code>, <code>clientY</code> are measurable properties.</p>
                     <p>In contrast <code>pointerId</code>, <code>pointerType</code>, <code>isPrimary</code>, and the
-                    [[UI-EVENTS]] Mouse Event model properties <code>button</code>, <code>buttons</code>, <code>ctrlKey</code>,
+                    [[UIEVENTS]] Mouse Event model properties <code>button</code>, <code>buttons</code>, <code>ctrlKey</code>,
                     <code>shiftKey</code>, <code>altKey</code>, and <code>metaKey</code> are not considered measurable properties,
                     as they don't relate to sensor data.</p>
                     </dd>