Wording change: drop links to File API's "object"

The default linking for [=object=] is to FileAPI's blob URL entry
object member[1], which is definitely wrong.

Replace such references with:

* Infra's ordered map[2], when a dictionary is intended, as that's
  what a JavaScript object is translated into via bindings.

* The generic phrase "platform object"

Referencing Web IDL's "object"[3] wouldn't be correct since that's
very specifically "non-null object references" meaning JS objects, and
which these aren't at this stage in the spec processing model.

[1] https://www.w3.org/TR/FileAPI/#blob-url-entry-object

[2] https://infra.spec.whatwg.org/#ordered-map

[3] https://webidl.spec.whatwg.org/#idl-object

Author: inexorabletash

index.bs

@@ -911,10 +911,10 @@ interface MLActivation {
     : <dfn>\[[builder]]</dfn> of type {{MLGraphBuilder}}
     ::
         The graph builder object this {{MLActivation}} belongs to.
-    : <dfn>\[[options]]</dfn> of type [=object=]
+    : <dfn>\[[options]]</dfn> of type [=ordered map=]
     ::
         A dictionary containing {{MLActivation}} options.
-    : <dfn>\[[operator]]</dfn> of type [=object=]
+    : <dfn>\[[operator]]</dfn> of type platform object
     ::
         Reference to {{MLActivation}}'s corresponding [=implementation-defined=] platform operator object.
   </dl>
@@ -6103,11 +6103,11 @@ interface MLOperand {};
     ::
         The {{MLOperand}}'s name (only for input operands).
 
-    : <dfn>\[[operand]]</dfn> of type [=object=]
+    : <dfn>\[[operand]]</dfn> of type platform object
     ::
         Reference to {{MLOperand}}'s corresponding [=implementation-defined=] platform operand object.
 
-    : <dfn>\[[operator]]</dfn> of type [=object=]
+    : <dfn>\[[operator]]</dfn> of type platform object
     ::
         Reference to {{MLOperand}}'s corresponding [=implementation-defined=] platform operator object.
   </dl>