Wording: Use shorter possessive form for abstract object properties (#565)

* Bug fix: Correct "rank of op's shape" to just "rank of op"

MLOperands have a rank; the shape just has a size.

* Wording: Use shorter possessive form for abstract object properties

Old and busted: ... the [=property=] of |object| ...
New hotness: ... |object|'s [=property=] ...
Discussed in #555 (comment)

* Bug fix: Dedupe some words

I noticed "then then" in the previous commit and searched for similar
glitches to fix.

* Bug fix: Incorrect referencing operand properties

* Erroneously referencing descriptor properties, but directly against
  an operand. This can be fixed by using the shape and dataType
  shortcuts. (6 cases)

* Simplifications where an operand's shape shortcut could be used. (3
  cases)

Author: inexorabletash

docs/SpecCodingConventions.md

@@ -54,7 +54,7 @@ Example:
 ```
     The <dfn>maximum size</dfn> of a collection is...
 
-    1. Let |max| be the [=maximum size=] of |collection|.
+    1. Let |max| be |collection|'s [=maximum size=].
 ```
 
 * When defining subsidiary terms, like properties of an object, members of an enum, etc, scope the definitions using `dfn-for` on the `dfn` or an ancestor.
@@ -96,6 +96,7 @@ Example:
 * Use `[=list/For each=] |index| in [=the range=] X to Y, inclusive` when iterating over a numeric range; a range is implicitly an ordered set which is a type of list. Specify _inclusive_ or _exclusive_ regarding the upper bound, for clarity.
 * Use "let" to introduce a variable and "set" to update a variable or assign to a property.
 * Use « » notation for literal lists, which helps make it clear that they are not JavaScript arrays.
+* When referring to abstract properties, use the short possessive form `|object|'s [=property=]`. Avoid the wordier `the [=property=] of |object|` form.
 
 
 ### Method Definitions