From 8e6e242863e483deead7fc49b3583d25ae7c63cb Mon Sep 17 00:00:00 2001 From: Javad Mokhtari Date: Sun, 25 Oct 2020 21:00:54 +0330 Subject: [PATCH] Update ch2.md --- get-started/ch2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/get-started/ch2.md b/get-started/ch2.md index 3f45da895..4c0670333 100644 --- a/get-started/ch2.md +++ b/get-started/ch2.md @@ -29,7 +29,7 @@ It may surprise you to consider separate .js files as separate JS programs. From | :--- | | Many projects use build process tools that end up combining separate files from the project into a single file to be delivered to a web page. When this happens, JS treats this single combined file as the entire program. | -The only way multiple standalone .js files act as a single program is by sharing their state (and access to their public functionality) via the "global scope." They mix together in this global scope namespace, so at runtime they act as as whole. +The only way multiple standalone .js files act as a single program is by sharing their state (and access to their public functionality) via the "global scope." They mix together in this global scope namespace, so at runtime they act as whole. Since ES6, JS has also supported a module format in addition to the typical standalone JS program format. Modules are also file-based. If a file is loaded via module-loading mechanism such as an `import` statement or a `