From c63ce1028662814114e730632b039f4ed1a711a5 Mon Sep 17 00:00:00 2001 From: Sudhir Kumar Ojha Date: Sat, 12 Oct 2019 19:37:37 +0530 Subject: [PATCH 1/2] Grammar issues fix Made some changes to make it more correct. --- 8-web-components/1-webcomponents-intro/article.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/8-web-components/1-webcomponents-intro/article.md b/8-web-components/1-webcomponents-intro/article.md index f9427462b3..8242a69ef4 100644 --- a/8-web-components/1-webcomponents-intro/article.md +++ b/8-web-components/1-webcomponents-intro/article.md @@ -57,14 +57,14 @@ Components may have subcomponents, e.g. messages may be parts of a higher-level How do we decide, what is a component? That comes from intuition, experience and common sense. Usually it's a separate visual entity that we can describe in terms of what it does and how it interacts with the page. In the case above, the page has blocks, each of them plays its own role, it's logical to make these components. A component has: -- its own JavaScript class. -- DOM structure, managed solely by its class, outside code doesn't access it ("encapsulation" principle). +- It's own JavaScript class. +- DOM structure, managed solely by it's class, outside code doesn't access it ("encapsulation" principle). - CSS styles, applied to the component. - API: events, class methods etc, to interact with other components. Once again, the whole "component" thing is nothing special. -There exist many frameworks and development methodologies to build them, each one with its own bells and whistles. Usually, special CSS classes and conventions are used to provide "component feel" -- CSS scoping and DOM encapsulation. +There exist many frameworks and development methodologies to build them, each one equipped with it's own bells and whistles. Usually, special CSS classes and conventions are used to provide "component feel" -- CSS scoping and DOM encapsulation. "Web components" provide built-in browser capabilities for that, so we don't have to emulate them any more. From 79a6361a03a6637a783a1ac01abf5e8c2cc2d950 Mon Sep 17 00:00:00 2001 From: Sudhir Kumar Ojha Date: Sun, 13 Oct 2019 17:13:54 +0530 Subject: [PATCH 2/2] Correct --- 8-web-components/1-webcomponents-intro/article.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/8-web-components/1-webcomponents-intro/article.md b/8-web-components/1-webcomponents-intro/article.md index 8242a69ef4..4bc14d542a 100644 --- a/8-web-components/1-webcomponents-intro/article.md +++ b/8-web-components/1-webcomponents-intro/article.md @@ -57,14 +57,14 @@ Components may have subcomponents, e.g. messages may be parts of a higher-level How do we decide, what is a component? That comes from intuition, experience and common sense. Usually it's a separate visual entity that we can describe in terms of what it does and how it interacts with the page. In the case above, the page has blocks, each of them plays its own role, it's logical to make these components. A component has: -- It's own JavaScript class. -- DOM structure, managed solely by it's class, outside code doesn't access it ("encapsulation" principle). +- Its own JavaScript class. +- DOM structure, managed solely by its class, outside code doesn't access it ("encapsulation" principle). - CSS styles, applied to the component. - API: events, class methods etc, to interact with other components. Once again, the whole "component" thing is nothing special. -There exist many frameworks and development methodologies to build them, each one equipped with it's own bells and whistles. Usually, special CSS classes and conventions are used to provide "component feel" -- CSS scoping and DOM encapsulation. +There exist many frameworks and development methodologies to build them, each one equipped with its own bells and whistles. Usually, special CSS classes and conventions are used to provide "component feel" -- CSS scoping and DOM encapsulation. "Web components" provide built-in browser capabilities for that, so we don't have to emulate them any more.