fixup! Normative: Rename integer types to match ECMAScript typed arrays

Co-authored-by: Darien Maillet Valentine <valentinium@gmail.com>

Author: ExE-Boss

index.bs

@@ -682,14 +682,14 @@ across [=IDL fragments=].
     <pre highlight="webidl">
         [Exposed=Window]
         interface B : A {
-          undefined f(SequenceOfLongs x);
+          undefined f(SequenceOfInt32s x);
         };
 
         [Exposed=Window]
         interface A {
         };
 
-        typedef sequence&lt;int32&gt; SequenceOfLongs;
+        typedef sequence&lt;int32&gt; SequenceOfInt32s;
     </pre>
 </div>
 
@@ -1694,7 +1694,7 @@ on which they appear.  It is language binding specific whether
     <pre highlight="webidl">
         [Exposed=Window]
         interface A {
-          const uint16 rambaldi = 47;
+          const int16 rambaldi = 47;
         };
     </pre>
 
@@ -7584,7 +7584,7 @@ In effect, where <var ignore>x</var> is a Number value,
         1.  If |signedness| is "<code>unsigned</code>", then let |lowerBound| be 0.
         1.  Otherwise let |lowerBound| be −2<sup>53</sup> + 1.
 
-            Note: this ensures {{int64}} types
+            Note: this ensures 64-bit [=integer types=]
             [=extended attribute associated with|associated with=] [{{EnforceRange}}] or
             [{{Clamp}}] [=extended attributes=] are representable in ECMAScript's [=Number type=]
             as unambiguous integers.