diff --git a/execution.html b/execution.html
index e40a7e4..8ca2a36 100644
--- a/execution.html
+++ b/execution.html
@@ -2386,7 +2386,7 @@
   <div class="head">
    <p data-fill-with="logo"></p>
    <h1 class="p-name no-ref" id="title">P2300R9<br><code class="highlight"><c- n>std</c-><c- o>::</c-><c- n>execution</c-></code></h1>
-   <h2 class="no-num no-toc no-ref heading settled" id="profile-and-date"><span class="content">Published Proposal, <time class="dt-updated" datetime="2024-05-21">2024-05-21</time></span></h2>
+   <h2 class="no-num no-toc no-ref heading settled" id="profile-and-date"><span class="content">Published Proposal, <time class="dt-updated" datetime="2024-05-25">2024-05-25</time></span></h2>
    <div data-fill-with="spec-metadata">
     <dl>
      <dt class="editor">Authors:
@@ -3899,7 +3899,7 @@ <h4 class="heading settled" data-level="1.9.2" id="intro-prior-art-coroutines"><
 allocations and indirections in the generated code.</p>
    <p>In a suite of generic async algorithms that are expected to be callable from hot
 code paths, the extra allocations and indirections are a deal-breaker. It is for
-these reasons that we consider coroutines a poor choise for a basis of all
+these reasons that we consider coroutines a poor choice for a basis of all
 standard async.</p>
    <h4 class="heading settled" data-level="1.9.3" id="intro-prior-art-callbacks"><span class="secno">1.9.3. </span><span class="content">Callbacks</span><a class="self-link" href="#intro-prior-art-callbacks"></a></h4>
    <p>Callbacks are the oldest, simplest, most powerful, and most efficient mechanism