From 47f119cabfc2eb7e524bc6584fd01328f9ce95d1 Mon Sep 17 00:00:00 2001 From: Stiliyan Lazarov Date: Sat, 4 Oct 2014 10:50:50 -0400 Subject: [PATCH] doc: fix wording and punctuation in modules [trev.norris@gmail.com: break lines at 80 characters] Signed-off-by: Trevor Norris --- doc/api/modules.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/api/modules.markdown b/doc/api/modules.markdown index 2e08ae1724..55d6accdf9 100644 --- a/doc/api/modules.markdown +++ b/doc/api/modules.markdown @@ -61,8 +61,8 @@ The module system is implemented in the `require("module")` module. -When there are circular `require()` calls, a module might not be -done being executed when it is returned. +When there are circular `require()` calls, a module might not have finished +executing when it is returned. Consider this situation: @@ -93,7 +93,7 @@ Consider this situation: When `main.js` loads `a.js`, then `a.js` in turn loads `b.js`. At that point, `b.js` tries to load `a.js`. In order to prevent an infinite -loop an **unfinished copy** of the `a.js` exports object is returned to the +loop, an **unfinished copy** of the `a.js` exports object is returned to the `b.js` module. `b.js` then finishes loading, and its `exports` object is provided to the `a.js` module. @@ -248,7 +248,7 @@ a global but rather local to each module. * {Object} The `module.exports` object is created by the Module system. Sometimes this is not -acceptable; many want their module to be an instance of some class. To do this +acceptable; many want their module to be an instance of some class. To do this, assign the desired export object to `module.exports`. Note that assigning the desired object to `exports` will simply rebind the local `exports` variable, which is probably not what you want to do.