diff --git a/Using-dojo-and-dojo-class-loading-in-jasmine-headless-webkit.md b/Using-dojo-and-dojo-class-loading-in-jasmine-headless-webkit.md
index 19baa86..6c4f714 100644
--- a/Using-dojo-and-dojo-class-loading-in-jasmine-headless-webkit.md
+++ b/Using-dojo-and-dojo-class-loading-in-jasmine-headless-webkit.md
@@ -39,9 +39,9 @@ dojo knows where to look for mystuff/SomethingCool.js in the load path.
 
 You do this by creating a global djConfig object before loading dojo.js, providing two key pieces of information.  One is modulePaths, which is how you tell dojo where to find things.  The other is baseScriptUri, which tells dojo where its home is.  
 
-Unlike djConfig.baseUrl, djConfig.baseScriptUri lets you specify the URL as a file URL, and dojo will load class files using file URLs instead of requiring a server.
+Unlike djConfig.baseUrl, djConfig.baseScriptUri lets you specify the URL as a file URL, and dojo will load  modules using file URLs instead of requiring a server.
 
-To create this global djConfig object, I include the test_bootstrap.js in the src_files list before dojo.js, which seems to ensure that test_bootstrap.js is run before dojo.js, thereby configuring dojo correctly when it loads.
+To create this global djConfig object before dojo initializes itself, I include the test_bootstrap.js in the src_files list before dojo.js, which seems to ensure that test_bootstrap.js is run before dojo.js, thereby configuring dojo correctly when it loads.
 
 ### Stop trying to load firebug.js