From fc3c0714db5e814bb4d59e4eefaa112b309e82dd Mon Sep 17 00:00:00 2001 From: Ilya Kantor Date: Mon, 24 May 2021 11:56:37 +0300 Subject: [PATCH] minor fixes --- 1-js/13-modules/01-modules-intro/article.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/1-js/13-modules/01-modules-intro/article.md b/1-js/13-modules/01-modules-intro/article.md index 2c9133f9..7e250faa 100644 --- a/1-js/13-modules/01-modules-intro/article.md +++ b/1-js/13-modules/01-modules-intro/article.md @@ -188,7 +188,7 @@ That's exactly because the module is executed only once. Exports are generated, In other words, a module can provide a generic functionality that needs a setup. E.g. authentication needs credentials. Then it can export a configuration object expecting the outer code to assign to it. -Here's a classical pattern: +Here's the classical pattern: 1. A module exports some means of configuration, e.g. a configuration object. 2. On the first import we initialize it, write to its properties. The top-level application script may do that. 3. Further imports use the module.