From 220bed3fd685b480667e1d006ff61d4c17815a1b Mon Sep 17 00:00:00 2001
From: Peter Roche <46547072+paroche@users.noreply.github.com>
Date: Thu, 13 Feb 2020 20:44:48 -0700
Subject: [PATCH] Update article.md

"From one hand" -> "On one hand"
---
 2-ui/99-ui-misc/03-event-loop/article.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/2-ui/99-ui-misc/03-event-loop/article.md b/2-ui/99-ui-misc/03-event-loop/article.md
index 779c6785..86e6146a 100644
--- a/2-ui/99-ui-misc/03-event-loop/article.md
+++ b/2-ui/99-ui-misc/03-event-loop/article.md
@@ -162,7 +162,7 @@ Another benefit of splitting heavy tasks for browser scripts is that we can show
 
 Usually the browser renders after the currently running code is complete. Doesn't matter if the task takes a long time. Changes to DOM are painted only after the task is finished.
 
-From one hand, that's great, because our function may create many elements, add them one-by-one to the document and change their styles -- the visitor won't see any "intermediate", unfinished state. An important thing, right?
+On one hand, that's great, because our function may create many elements, add them one-by-one to the document and change their styles -- the visitor won't see any "intermediate", unfinished state. An important thing, right?
 
 Here's the demo, the changes to `i` won't show up until the function finishes, so we'll see only the last value: