util: fix comment typos

When the deep(Strict)Equal comparison functions were moved to an
internal module, a variable named `current` was replaced with `val1`.
That accidentally also replaced a few "currently"s in comments.

Refs: #16084

PR-URL: #21436
Reviewed-By: Daniel Bevenius <[email protected]>
Reviewed-By: Weijia Wang <[email protected]>
Reviewed-By: Colin Ihrig <[email protected]>
Reviewed-By: Ruben Bridgewater <[email protected]>
Reviewed-By: James M Snell <[email protected]>
Reviewed-By: Tobias Nießen <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Trivikram Kamat <[email protected]>

lib/internal/util/comparisons.js

@@ -287,7 +287,7 @@ function setHasEqualElement(set, val1, strict, memo) {
   return false;
 }
 
-// Note: we val1ly run this multiple times for each loose key!
+// Note: we currently run this multiple times for each loose key!
 // This is done to prevent slowing down the average case.
 function setHasLoosePrim(a, b, val) {
   const altValues = findLooseMatchingPrimitives(val);
@@ -381,9 +381,9 @@ function findLooseMatchingPrimitives(prim) {
 }
 
 // This is a ugly but relatively fast way to determine if a loose equal entry
-// val1ly has a correspondent matching entry. Otherwise checking for such
+// currently has a correspondent matching entry. Otherwise checking for such
 // values would be way more expensive (O(n^2)).
-// Note: we val1ly run this multiple times for each loose key!
+// Note: we currently run this multiple times for each loose key!
 // This is done to prevent slowing down the average case.
 function mapHasLoosePrim(a, b, key1, memo, item1, item2) {
   const altKeys = findLooseMatchingPrimitives(key1);