@@ -118,7 +118,7 @@ with at the time and forget to also fix it in the other program.
118118
119119(((duplication)))Once you have lots of such shared, duplicated pieces
120120of code, you will find yourself wasting a lot of time and energy on
121- moving them around and keeping them up to date.
121+ moving them around and keeping them up-to- date.
122122
123123(((reuse)))Putting pieces of functionality that stand on their own
124124into separate files and modules makes them easier to track, update,
@@ -481,11 +481,11 @@ global variable (`require`) to allow modules to find and use each
481481other without going through the ((global scope)).
482482
483483This style of module system is called _((CommonJS)) modules_, after
484- the pseudo((standard)) that first specified it. It is built into the
484+ the pseudo- ((standard)) that first specified it. It is built into the
485485((Node.js)) system. Real implementations do a lot more than the
486486example I showed. Most importantly, they have a much more intelligent
487487way of going from a module name to an actual piece of code, allowing
488- both path names relative to the current file and module names that
488+ both pathnames relative to the current file and module names that
489489point directly to locally installed modules.
490490
491491[[amd]]
@@ -663,7 +663,7 @@ code executes.
663663
664664A real ((AMD)) implementation is, again, quite a lot more clever about
665665resolving module names to actual URLs and generally more robust than
666- the one shown previously. The _((RequireJS))_ (_requirejs.org_) project provides
666+ the one shown previously. The _((RequireJS))_ (http://requirejs.org[ _requirejs.org_] ) project provides
667667a popular implementation of this style of ((module loader)).
668668
669669== Interface design ==
@@ -716,7 +716,7 @@ expects a real array won't be able to work with them. This is an
716716example of poor __composability__—the module cannot be easily composed
717717with other code.
718718
719- (((encapsulation)))(((spell-check example)))An example would be a
719+ (((encapsulation)))(((spell-check example)))One example would be a
720720module for spell-checking text, which we might need when we want to
721721write a text editor. The spell-checker could be made to operate
722722directly on whichever complicated ((data structure))s the editor uses
@@ -840,7 +840,7 @@ Tiger
840840(((book analogy)))Don't exaggerate and create too many modules. A book
841841that starts a new chapter for every page would probably get on your
842842nerves, if only because of all the space wasted on titles. Similarly,
843- having to open ten files to read a tiny project isn't helpful. Aim for
843+ having to open 10 files to read a tiny project isn't helpful. Aim for
844844three to five modules.
845845
846846(((encapsulation)))You can choose to have some functions become
0 commit comments