From cb416aa79a363ac7c21f6ac891ab4de6e90b9755 Mon Sep 17 00:00:00 2001 From: simmayor Date: Wed, 12 Dec 2018 15:56:52 -0500 Subject: [PATCH] Grammar --- 2-ui/4-forms-controls/2-focus-blur/article.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/2-ui/4-forms-controls/2-focus-blur/article.md b/2-ui/4-forms-controls/2-focus-blur/article.md index 3177ee39..1a880ce4 100644 --- a/2-ui/4-forms-controls/2-focus-blur/article.md +++ b/2-ui/4-forms-controls/2-focus-blur/article.md @@ -49,7 +49,7 @@ Your email please: ``` -Modern HTML allows to do many validations using input attributes: `required`, `pattern` and so on. And sometimes they are just what we need. JavaScript can be used when we want more flexibility. Also we could automatically send the changed value on the server if it's correct. +Modern HTML allows to do many validations using input attributes: `required`, `pattern` and so on. And sometimes they are just what we need. JavaScript can be used when we want more flexibility. Also we could automatically send the changed value to the server if it's correct. ## Methods focus/blur @@ -100,7 +100,7 @@ One of them is when the visitor clicks somewhere else. But also JavaScript itsel These features sometimes cause `focus/blur` handlers to misbehave -- to trigger when they are not needed. -The best recipe is to be careful when using these events. If we want to track user-initiated focus-loss, then we should evade causing it by ourselves. +The best recipe is to be careful when using these events. If we want to track user-initiated focus-loss, then we should avoid causing it ourselves. ``` ## Allow focusing on any element: tabindex