fixup: "execution context" -> "ExecutionContext Record" in some prose

spec.html

@@ -11670,7 +11670,7 @@ <h1>Execution Contexts</h1>
             a Module Record, a Script Record, or *null*
           </td>
           <td>
-            The Module Record or Script Record from which associated code originates. If there is no originating script or module, as is the case for the original execution context created in InitializeHostDefinedRealm, the value is *null*.
+            The Module Record or Script Record from which associated code originates. If there is no originating script or module, as is the case for the original ExecutionContext Record created in InitializeHostDefinedRealm, the value is *null*.
           </td>
         </tr>
       </table>
@@ -11876,18 +11876,18 @@ <h1>Jobs and Host Operations to Enqueue Jobs</h1>
     <p>At any particular time, _scriptOrModule_ (a Script Record, a Module Record, or *null*) is the <dfn id="job-activescriptormodule">active script or module</dfn> if all of the following conditions are true:</p>
     <ul>
       <li>GetActiveScriptOrModule() is _scriptOrModule_.</li>
-      <li>If _scriptOrModule_ is a Script Record or Module Record, let _ec_ be the topmost execution context on the execution context stack whose [[ScriptOrModule]] field is _scriptOrModule_. _ec_.[[Realm]] is _scriptOrModule_.[[Realm]].</li>
+      <li>If _scriptOrModule_ is a Script Record or Module Record, let _ec_ be the topmost ExecutionContext Record on the execution context stack whose [[ScriptOrModule]] field is _scriptOrModule_. _ec_.[[Realm]] is _scriptOrModule_.[[Realm]].</li>
     </ul>
 
     <p>At any particular time, an execution is <dfn id="job-preparedtoevaluatecode">prepared to evaluate ECMAScript code</dfn> if all of the following conditions are true:</p>
     <ul>
       <li>The execution context stack is not empty.</li>
-      <li>The [[Realm]] field of the topmost execution context on the execution context stack is a Realm Record.</li>
+      <li>The [[Realm]] field of the topmost ExecutionContext Record on the execution context stack is a Realm Record.</li>
     </ul>
 
     <emu-note>
-      <p>Host environments may prepare an execution to evaluate code by pushing execution contexts onto the execution context stack. The specific steps are implementation-defined.</p>
-      <p>The specific choice of Realm is up to the host environment. This initial execution context and Realm is only in use before any callback function is invoked. When a callback function related to a Job, like a Promise handler, is invoked, the invocation pushes its own execution context and Realm.</p>
+      <p>Host environments may prepare an execution to evaluate code by pushing ExecutionContext Records onto the execution context stack. The specific steps are implementation-defined.</p>
+      <p>The specific choice of Realm is up to the host environment. This initial ExecutionContext Record and Realm is only in use before any callback function is invoked. When a callback function related to a Job, like a Promise handler, is invoked, the invocation pushes its own ExecutionContext Record and Realm.</p>
     </emu-note>
 
     <p>Particular kinds of Jobs have additional conformance requirements.</p>