diff --git a/packages/spark/spark.js b/packages/spark/spark.js
index a823146d37..2b085b2640 100644
--- a/packages/spark/spark.js
+++ b/packages/spark/spark.js
@@ -541,7 +541,7 @@ Spark.renderToRange = function (range, htmlFunc) {
 
   var results = {};
 
-  // patch (using preservations)
+  // Patch! (using preservations)
   range.operate(function (start, end) {
     // XXX this will destroy all liveranges, including ones
     // inside constant regions whose DOM nodes we are going
@@ -549,8 +549,8 @@ Spark.renderToRange = function (range, htmlFunc) {
     Spark.finalize(start, end);
     // Disable events during patching.  If we don't do this, patching
     // a checkbox in old IE will cause "change" events to fire on the
-    // partially-patched DOM.  Since the liverange tree needn't be
-    // well-formed, delivering events mid-patch is never right.
+    // partially-patched DOM.  Since the LiveRange tree needn't even
+    // be well-formed, delivering events mid-patch is never right.
     Spark._eventsDisabled.withValue(true, function () {
       Spark._patch(start.parentNode, frag, start.previousSibling,
                    end.nextSibling, preservations, results);
diff --git a/packages/spark/spark_tests.js b/packages/spark/spark_tests.js
index 60dfa4d029..e34708f24e 100644
--- a/packages/spark/spark_tests.js
+++ b/packages/spark/spark_tests.js
@@ -2616,7 +2616,8 @@ Tinytest.add("spark - controls", function(test) {
         // IE 7 is known to fire change events on all
         // the radio buttons with checked=false, as if
         // each button were deselected before selecting
-        // the new one.
+        // the new one.  (Meteor doesn't normalize this
+        // behavior.)
         // However, browsers are consistent if we are
         // getting a checked=true notification.
         var btn = event.target;