diff --git a/arndt/move_to_informational/draft-ietf-wimse-client-assertion-in-workload-environments.html b/arndt/move_to_informational/draft-ietf-wimse-client-assertion-in-workload-environments.html
index 5b8c03c..c731558 100644
--- a/arndt/move_to_informational/draft-ietf-wimse-client-assertion-in-workload-environments.html
+++ b/arndt/move_to_informational/draft-ietf-wimse-client-assertion-in-workload-environments.html
@@ -1033,7 +1033,7 @@
 </tr></thead>
 <tfoot><tr>
 <td class="left">Hofmann, et al.</td>
-<td class="center">Expires 24 April 2025</td>
+<td class="center">Expires 25 April 2025</td>
 <td class="right">[Page]</td>
 </tr></tfoot>
 </table>
@@ -1046,12 +1046,12 @@
 <dd class="internet-draft">draft-ietf-wimse-client-assertion-in-workload-environments-latest</dd>
 <dt class="label-published">Published:</dt>
 <dd class="published">
-<time datetime="2024-10-21" class="published">21 October 2024</time>
+<time datetime="2024-10-22" class="published">22 October 2024</time>
     </dd>
 <dt class="label-intended-status">Intended Status:</dt>
 <dd class="intended-status">Informational</dd>
 <dt class="label-expires">Expires:</dt>
-<dd class="expires"><time datetime="2025-04-24">24 April 2025</time></dd>
+<dd class="expires"><time datetime="2025-04-25">25 April 2025</time></dd>
 <dt class="label-authors">Authors:</dt>
 <dd class="authors">
 <div class="author">
@@ -1102,7 +1102,7 @@ <h2 id="name-status-of-this-memo">
         time. It is inappropriate to use Internet-Drafts as reference
         material or to cite them other than as "work in progress."<a href="#section-boilerplate.1-3" class="pilcrow">¶</a></p>
 <p id="section-boilerplate.1-4">
-        This Internet-Draft will expire on 24 April 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
+        This Internet-Draft will expire on 25 April 2025.<a href="#section-boilerplate.1-4" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="copyright">
@@ -1759,7 +1759,7 @@ <h3 id="name-secure-production-identity-">
 <a href="#appendix-A.2" class="section-number selfRef">A.2. </a><a href="#name-secure-production-identity-" class="section-name selfRef">Secure Production Identity Framework For Everyone (SPIFFE)</a>
         </h3>
 <p id="appendix-A.2-1">Secure Production Identity Framework For Everyone, also known as SPIFFE, is a cloud native compute foundation (CNCF) adopted project which defines an API defined called "Workload API" to delivery machine identity to workloads. Workloads can retrieve either X509 based or JWT credentials without the need to authenticate making it very easy to use. How workloads authenticate on the API is not part of the specification. It is common to use platform metadata from the operating system and the workload platform for authentication on the Workload API.<a href="#appendix-A.2-1" class="pilcrow">¶</a></p>
-<p id="appendix-A.2-2">For the scope of this document, the JWT formatted credential is the most relevant one. SPIFFE referres to it as "JWT-SVID" (JWT - Single Verifyable Identity Document).<a href="#appendix-A.2-2" class="pilcrow">¶</a></p>
+<p id="appendix-A.2-2">For the scope of this document, the JWT formatted credential is the most relevant one. SPIFFE referres to it as "JWT-SVID" (JWT - SPIFFE Verifiable Identity Document).<a href="#appendix-A.2-2" class="pilcrow">¶</a></p>
 <p id="appendix-A.2-3">Workloads are required to specify at least one audience when requesting a JWT-SVID from the Workload API.<a href="#appendix-A.2-3" class="pilcrow">¶</a></p>
 <p id="appendix-A.2-4">To allow validation, SPIFFE offers<a href="#appendix-A.2-4" class="pilcrow">¶</a></p>
 <ul class="normal">
diff --git a/arndt/move_to_informational/draft-ietf-wimse-client-assertion-in-workload-environments.txt b/arndt/move_to_informational/draft-ietf-wimse-client-assertion-in-workload-environments.txt
index adc8293..2b04316 100644
--- a/arndt/move_to_informational/draft-ietf-wimse-client-assertion-in-workload-environments.txt
+++ b/arndt/move_to_informational/draft-ietf-wimse-client-assertion-in-workload-environments.txt
@@ -5,13 +5,13 @@
 WIMSE                                                         B. Hofmann
 Internet-Draft                                             H. Tschofenig
 Intended status: Informational                                   Siemens
-Expires: 24 April 2025                                       E. Giordano
+Expires: 25 April 2025                                       E. Giordano
                                                                    Nokia
                                                             Y. Rosomakho
                                                                  Zscaler
                                                       A. Schwenkschuster
                                                                    SPIRL
-                                                         21 October 2024
+                                                         22 October 2024
 
 
           OAuth 2.0 Client Assertion in Workload Environments
@@ -47,7 +47,7 @@ Status of This Memo
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on 24 April 2025.
+   This Internet-Draft will expire on 25 April 2025.
 
 Copyright Notice
 
@@ -527,8 +527,8 @@ A.2.  Secure Production Identity Framework For Everyone (SPIFFE)
    Workload API.
 
    For the scope of this document, the JWT formatted credential is the
-   most relevant one.  SPIFFE referres to it as "JWT-SVID" (JWT - Single
-   Verifyable Identity Document).
+   most relevant one.  SPIFFE referres to it as "JWT-SVID" (JWT - SPIFFE
+   Verifiable Identity Document).
 
    Workloads are required to specify at least one audience when
    requesting a JWT-SVID from the Workload API.