From 9967f336ca32e8a6d48d010f3a28a4658bc2f92c Mon Sep 17 00:00:00 2001
From: Michael Dyck <jmdyck@ibiblio.org>
Date: Wed, 15 Feb 2023 20:08:53 -0500
Subject: [PATCH] fixup: Insert "and async functions" into note re execution
 contexts

---
 spec.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec.html b/spec.html
index 5bef5127f5e..d5fabf6f8ab 100644
--- a/spec.html
+++ b/spec.html
@@ -11694,7 +11694,7 @@ <h1>Execution Contexts</h1>
       <h1>Execution Context Stack</h1>
       <p>An agent's <dfn id="execution-context-stack" variants="execution context stacks">execution context stack</dfn> is used to organize some or all of the agent's execution contexts. The running execution context is always the top element of this stack.</p>
       <p>Adding and removing always happens at the “top” of the execution context stack. When an execution context is added, it becomes the topmost (i.e., the running execution context), and when it is later removed, the execution context “below” it becomes topmost again.</p>
-      <emu-note>In the absense of generators, every execution context that is pushed onto the stack is new, and when it's removed from the stack it can be discarded. With generators, some execution contexts outlive their time on the stack, exist for a while outside the stack, and then later are pushed onto the stack again.</emu-note>
+      <emu-note>In the absence of generators and async functions, every execution context that is pushed onto the stack is new, and when it's removed from the stack it can be discarded. With generators and async functions, some execution contexts outlive their time on the stack, exist for a while outside the stack, and then later are pushed onto the stack again.</emu-note>
     </emu-clause>
 
     <emu-clause id="sec-getactivescriptormodule" type="abstract operation">