Normalize requirejs/require calls

See requirejs/requirejs#428 (comment)

README.md

@@ -63,12 +63,12 @@ As you do builds and see in the build output that each page is including the
 same module, add it to common's "include" array in **tools/build.js**.
 
 It is better to add these common modules to the **tools/build.js** config
-instead of doing a require([]) call for them in **js/common.js**. Modules that
+instead of doing a requirejs([]) call for them in **js/common.js**. Modules that
 are not explicitly required at runtime are not executed when added to common.js
 via the include build option. So by using **tools/build.js**, you can include
 common modules that may be in 2-3 pages but not all pages. For pages that do
 not need a particular common module, it will not be executed. If you put in a
-require() call for it in **js/common.js**, then it will always be executed.
+requirejs() call for it in **js/common.js**, then it will always be executed.
 
 ## More info
 

tools/build.js

@@ -27,7 +27,7 @@
         //listed before the build layer that wants to exclude it.
         //"include" the appropriate "app/main*" module since by default
         //it will not get added to the build since it is loaded by a nested
-        //require in the page*.js files.
+        //requirejs in the page*.js files.
         {
             //module names are relative to baseUrl/paths config
             name: '../page1',

www/js/page1.js

@@ -1,4 +1,4 @@
 //Load common code that includes config, then load the app logic for this page.
-require(['./common'], function (common) {
-    require(['app/main1']);
+requirejs(['./common'], function (common) {
+    requirejs(['app/main1']);
 });

www/js/page2.js

@@ -1,4 +1,4 @@
 //Load common code that includes config, then load the app logic for this page.
-require(['./common'], function (common) {
-    require(['app/main2']);
+requirejs(['./common'], function (common) {
+    requirejs(['app/main2']);
 });