Apply suggestions from code review

mdn · Dec 2, 2023 · dae68a9 · dae68a9
1 parent d3b9e08
commit dae68a9
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/files/en-us/web/api/element/pointercancel_event/index.md b/files/en-us/web/api/element/pointercancel_event/index.md
@@ -16,7 +16,7 @@ Some examples of situations that will trigger a `pointercancel` event:
 - The device's screen orientation is changed while the pointer is active.
 - The browser decides that the user started pointer input accidentally. This can happen if, for example, the hardware supports palm rejection to prevent a hand resting on the display while using a stylus from accidentally triggering events.
 - The {{cssxref("touch-action")}} CSS property prevents the input from continuing.
-- When the user interacted with too many simultaneous pointers the browser can fire this event for all existing pointers (even if they are still touching the screen).
+- When the user interacts with too many simultaneous pointers, the browser can fire this event for all existing pointers (even if the user is still touching the screen).
 
 > **Note:** After the `pointercancel` event is fired, the browser will also send {{domxref("Element/pointerout_event", "pointerout")}} followed by {{domxref("Element/pointerleave_event", "pointerleave")}}.
 

diff --git a/files/en-us/web/api/element/touchcancel_event/index.md b/files/en-us/web/api/element/touchcancel_event/index.md
@@ -16,7 +16,7 @@ Some examples of situations that will trigger a `touchcancel` event:
 - The device's screen orientation is changed while the touch is active.
 - The browser decides that the user started touch input accidentally. This can happen if, for example, the hardware supports palm rejection to prevent a hand resting on the display while using a stylus from accidentally triggering events.
 - The {{cssxref("touch-action")}} CSS property prevents the input from continuing.
-- When the user interacted with too many simultaneous fingers the browser can fire this event for all existing pointers (even if they are still touching the screen).
+- When the user interacts with too many fingers simultaneously, the browser can fire this event for all existing pointers (even if the user is still touching the screen).
 
 ## Syntax