From 29a3c58d72b8f10f9f1f9ce5cf691d2ab44a9d01 Mon Sep 17 00:00:00 2001 From: Ilya Kantor Date: Sat, 11 May 2019 11:29:50 +0300 Subject: [PATCH] fixes --- 2-ui/3-event-details/5-keyboard-events/article.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/2-ui/3-event-details/5-keyboard-events/article.md b/2-ui/3-event-details/5-keyboard-events/article.md index aad83911..afaa50bf 100644 --- a/2-ui/3-event-details/5-keyboard-events/article.md +++ b/2-ui/3-event-details/5-keyboard-events/article.md @@ -110,9 +110,9 @@ So, to reliably track layout-dependent characters, `event.key` may be a better w ## Auto-repeat -If a key is being pressed for a long enough time, it starts to repeat: the `keydown` triggers again and again, and then when it's released we finally get `keyup`. So it's kind of normal to have many `keydown` and a single `keyup`. +If a key is being pressed for a long enough time, it starts to "auto-repeat": the `keydown` triggers again and again, and then when it's released we finally get `keyup`. So it's kind of normal to have many `keydown` and a single `keyup`. -For all repeating keys the event object has `event.repeat` property set to `true`. +For events triggered by auto-repeat, the event object has `event.repeat` property set to `true`. ## Default actions