Editorial: some minor rewordings

spec.html

@@ -45388,7 +45388,7 @@ <h1>
           1. Return _final_.
         </emu-alg>
         <emu-note>
-          <p>The representation of arrays includes only the elements in the interval from *+0*<sub>𝔽</sub> (inclusive) to `array.length` (exclusive). Properties whose keys are not Uint32-strings are excluded from the stringification. An array is stringified as an opening LEFT SQUARE BRACKET, elements separated by COMMA, and a closing RIGHT SQUARE BRACKET.</p>
+          <p>The representation of arrays includes only the elements in the interval from *+0*<sub>𝔽</sub> (inclusive) to `array.length` (exclusive). Any property whose key is not a Uint32-string is excluded from the stringification. An array is stringified as an opening LEFT SQUARE BRACKET, elements separated by COMMA, and a closing RIGHT SQUARE BRACKET.</p>
         </emu-note>
       </emu-clause>
     </emu-clause>
@@ -50795,7 +50795,7 @@ <h1>The Strict Mode of ECMAScript</h1>
       Arguments objects for strict functions define a non-configurable accessor property *"callee"* which throws a *TypeError* exception on access (<emu-xref href="#sec-createunmappedargumentsobject"></emu-xref>).
     </li>
     <li>
-      Arguments objects for strict functions do not dynamically share their Uint32-indexed property values with the corresponding formal parameter bindings of their functions. (<emu-xref href="#sec-arguments-exotic-objects"></emu-xref>).
+      Arguments objects for strict functions do not dynamically share the values of their Uint32-indexed properties with the corresponding formal parameter bindings of their functions. (<emu-xref href="#sec-arguments-exotic-objects"></emu-xref>).
     </li>
     <li>
       For strict functions, if an arguments object is created the binding of the local identifier `arguments` to the arguments object is immutable and hence may not be the target of an assignment expression. (<emu-xref href="#sec-functiondeclarationinstantiation"></emu-xref>).