From 7a0fbdb4073f5e405bf675f0d12194020b8ff559 Mon Sep 17 00:00:00 2001
From: paroche <46547072+paroche@users.noreply.github.com>
Date: Mon, 21 Oct 2019 14:11:56 -0600
Subject: [PATCH] Update article.md

Take 2 on 'There should be "loading" indications...." line.
---
 2-ui/5-loading/02-script-async-defer/article.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/2-ui/5-loading/02-script-async-defer/article.md b/2-ui/5-loading/02-script-async-defer/article.md
index 95e31d17..ca82a730 100644
--- a/2-ui/5-loading/02-script-async-defer/article.md
+++ b/2-ui/5-loading/02-script-async-defer/article.md
@@ -191,7 +191,7 @@ Please note that if you're using `defer`, then the page is visible *before* the
 
 So the user may read the page, but some graphical components are probably not ready yet.
 
-There should be "loading" indications in the proper places, and not-working buttons should be visually disabled, to clearly show the user what's ready and what's not.
+There should be "loading" indications in the proper places, and disabled buttons should show as such, so the user can clearly see what's ready and what's not.
 ```
 
 In practice, `defer` is used for scripts that need the whole DOM and/or their relative execution order is important. And  `async` is used for independent scripts, like counters or ads. And their relative execution order does not matter.