diff --git a/Vik_comments_to_editor.adoc b/Vik_comments_to_editor.adoc
index f69feb40..b9791528 100644
--- a/Vik_comments_to_editor.adoc
+++ b/Vik_comments_to_editor.adoc
@@ -20,6 +20,10 @@ My notes:
 * p. 338 V: AMD is a standard. There is no such thing as AMD modules for RequireJS
 * p. 346 V: I don't understand the questions?
 
+from +Chapters 10-12.pdf+ document
+
+* p. 347 example of require.js plugins provided in a prev section with code example usage. I don't understand the issue.
+
 == Chapter 8
 
 * p. 358 V: Mentioned slide deck demonstrates how to use PhantomJS for performance testing.
@@ -30,4 +34,9 @@ My notes:
 * p. 372 explanation followed in callouts
 * p. 374 this concept introduced now
 * p. 380 grunt watch task described in tools chapter
-* p. 386 in spirit of tdd spec goes first. Code goes after.
\ No newline at end of file
+* p. 386 in spirit of tdd spec goes first. Code goes after.
+
+from +Chapters 10-12.pdf+ document
+
+* p. 359 inconsistency addressed in a favor of JSHint.
+* p. 396 I don't understand what editor meant here.
\ No newline at end of file
diff --git a/ch8_testdriven_js.asciidoc b/ch8_testdriven_js.asciidoc
index 9e7e063d..fc562d6e 100644
--- a/ch8_testdriven_js.asciidoc
+++ b/ch8_testdriven_js.asciidoc
@@ -359,7 +359,7 @@ Now let's update the Grunfile to run the same sample specifications with the Pha
 [[FIG-3]]
 image::fig_08_03.png[]
 
-Now you need to edit Gruntfile.js to activate Jasmine support.
+Now you need to edit Gruntfile_jasmine.js to activate Jasmine support.
 
 .Gruntfile_jasmine.js with Jasmine running support 
 [source,javascript]
@@ -1233,7 +1233,7 @@ image::fig_08_12.png[]
 
 Testing is one of the most important processes of software development. Well organized testing helps keeping the code in a good and working state. It's especially important in interpreted languages like JavaSctipt where there is no compiler to provide a helping hand to find lots of errors on very early stages. 
 
-In this situation, static code analysis tools, like JSHint, could become very handy in helping with identifying typos and enforcing best practices accepted by the JavaScript community.
+In this situation, static code analysis tools, like JSHint (discussed in «Selected Productivity Tools for Enterprise Developers» chapter), could become very handy in helping with identifying typos and enforcing best practices accepted by the JavaScript community.
 
 In enterprise projects developed with compiled languages people often debate if test-driven development is really beneficial. With JavaScript it's non-debatable unless you have unlimited time and budget and are ready to live with unmaintainable JavaScript.