From f8053dfc8b8a3804ee854c614a6210ec416c8ced Mon Sep 17 00:00:00 2001
From: Richard Gibson <richard.gibson@gmail.com>
Date: Sun, 15 Aug 2021 19:46:41 -0700
Subject: [PATCH] Editorial: Improve `next` method definition consistency
 (#2485)

---
 spec.html | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/spec.html b/spec.html
index 2c495dc78a..74df5981ad 100644
--- a/spec.html
+++ b/spec.html
@@ -37452,7 +37452,6 @@ <h1>The %ArrayIteratorPrototype% Object</h1>
 
         <emu-clause id="sec-%arrayiteratorprototype%.next">
           <h1>%ArrayIteratorPrototype%.next ( )</h1>
-          <p>When the `next` method is called, the following steps are taken:</p>
           <emu-alg>
             1. Return ? GeneratorResume(*this* value, ~empty~, *"%ArrayIteratorPrototype%"*).
           </emu-alg>
@@ -43940,10 +43939,8 @@ <h1>Generator.prototype.constructor</h1>
 
       <emu-clause id="sec-generator.prototype.next">
         <h1>Generator.prototype.next ( _value_ )</h1>
-        <p>The `next` method performs the following steps:</p>
         <emu-alg>
-          1. Let _g_ be the *this* value.
-          1. Return ? GeneratorResume(_g_, _value_, ~empty~).
+          1. Return ? GeneratorResume(*this* value, _value_, ~empty~).
         </emu-alg>
       </emu-clause>