From 5e7a370476d9c39605d325f655871bed2a0c0b11 Mon Sep 17 00:00:00 2001 From: Egor Zotov Date: Mon, 24 Jun 2019 00:38:43 +1000 Subject: [PATCH] Fix a mistake --- .../04-private-protected-properties-methods/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/1-js/09-classes/04-private-protected-properties-methods/article.md b/1-js/09-classes/04-private-protected-properties-methods/article.md index 78d6c78f..13bf0359 100644 --- a/1-js/09-classes/04-private-protected-properties-methods/article.md +++ b/1-js/09-classes/04-private-protected-properties-methods/article.md @@ -322,7 +322,7 @@ Hiding complexity **It's always convenient when implementation details are hidden, and a simple, well-documented external interface is available.** -To hide internal interface we use either protected or public properties: +To hide internal interface we use either protected or private properties: - Protected fields start with `_`. That's a well-known convention, not enforced at the language level. Programmers should only access a field starting with `_` from its class and classes inheriting from it. - Private fields start with `#`. JavaScript makes sure we only can access those from inside the class.