From 676ffb718a7309e3a3d10c275777873588f2726b Mon Sep 17 00:00:00 2001 From: paroche <46547072+paroche@users.noreply.github.com> Date: Sat, 19 Oct 2019 21:15:54 -0600 Subject: [PATCH] Update article.md Wording on why use attribute vs classes question --- 2-ui/1-document/06-dom-attributes-and-properties/article.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/2-ui/1-document/06-dom-attributes-and-properties/article.md b/2-ui/1-document/06-dom-attributes-and-properties/article.md index 955277b6..74adb439 100644 --- a/2-ui/1-document/06-dom-attributes-and-properties/article.md +++ b/2-ui/1-document/06-dom-attributes-and-properties/article.md @@ -298,9 +298,9 @@ For instance, here for the order state the attribute `order-state` is used: ``` -Why the attribute may be preferable to classes like `.order-state-new`, `.order-state-pending`, `order-state-canceled`? +Why would using an attribute be preferable to having classes like `.order-state-new`, `.order-state-pending`, `order-state-canceled`? -That's because an attribute is more convenient to manage. The state can be changed as easy as: +Because an attribute is more convenient to manage. The state can be changed as easy as: ```js // a bit simpler than removing old/adding a new class