tweaking some wording around integer-looking strings as property names, to be more precise (per #1791)

Author: getify

objects-classes/ch1.md

@@ -125,24 +125,25 @@ myObj = {
 
 ### Property Names
 
-Property names in object literals are almost always treated/coeced as string values. One exception to this is for numeric (or "numeric looking") property "names":
+Property names in object literals are almost always treated/coeced as string values. One exception to this is for integer (or "integer looking") property "names":
 
 ```js
 anotherObj = {
-    42: "<-- this property name will remain a number",
-    "41": "<-- this property name will be coerced to a number",
-    true: "<-- this property name will be converted to a string",
-    myObj: "<-- ...and so will this one"
+    42:       "<-- this property name will be treated as an integer",
+    "41":     "<-- ...and so will this one",
+
+    true:     "<-- this property name will be treated as a string",
+    [myObj]:  "<-- ...and so will this one"
 };
 ```
 
-The `42` property name will remain a number, and the `"41"` string value will be coerced to a numeric property name since it *looks like* a number. By contrast, the `true` value will become the string property name `"true"`, and the `myObj` identifier reference will coerce the object's value to a string (generally the default `"[object Object]"`).
+The `42` property name will be treated as an integer property name (aka, index); the `"41"` string value will also be treated as such since it *looks like* an integer. By contrast, the `true` value will become the string property name `"true"`, and the `myObj` identifier reference, *computed* via the surrounding `[ .. ]`, will coerce the object's value to a string (generally the default `"[object Object]"`).
 
 | WARNING: |
 | :--- |
-| If you need to actually use an object as a key/property name, never rely on this string coercion; its behavior is surprising and almost certainly not what's expected, so program bugs are likely to occur. Instead, use a more specialized data structure, called a `Map` (added in ES6), where objects used as property "names" are left as-is instead of being coerced to a string value. |
+| If you need to actually use an object as a key/property name, never rely on this computed string coercion; its behavior is surprising and almost certainly not what's expected, so program bugs are likely to occur. Instead, use a more specialized data structure, called a `Map` (added in ES6), where objects used as property "names" are left as-is instead of being coerced to a string value. |
 
-You can also *compute* the **property name** (distinct from computing the property value) at the time of object literal definition:
+As with with `[myObj]` above, you can *compute* any **property name** (distinct from computing the property value) at the time of object literal definition:
 
 ```js
 anotherObj = {

objects-classes/ch2.md

@@ -148,14 +148,14 @@ myList[0];      // 23
 myList[1];      // 42
 ```
 
-Recall that any string property name on an object that "looks like" a number -- is able to be validly coerced to a string -- will actually be treated like a number. The same goes for arrays. You should always use `42` as a numeric index (aka, property name), but if you use the string `"42"`, JS will coerce that to a number for you.
+Recall that any string property name on an object that "looks like" an integer -- is able to be validly coerced to a numeric integer -- will actually be treated like an integer property (aka, integer index). The same goes for arrays. You should always use `42` as an integer index (aka, property name), but if you use the string `"42"`, JS will assume you meant that as an integer and do that for you.
 
 ```js
-// "2" works as an index here, but it's not advised
+// "2" works as an integer index here, but it's not advised
 myList["2"];    // 109
 ```
 
-One exception to the "no named properties on arrays" rule is that all arrays automatically expose a `length` property, which is automatically kept updated with the "length" of the array.
+One exception to the "no named properties on arrays" *rule* is that all arrays automatically expose a `length` property, which is automatically kept updated with the "length" of the array.
 
 ```js
 myList = [ 23, 42, 109 ];