diff --git a/math-2023.html b/math-2023.html
index d58cfe48..7f18e3dd 100644
--- a/math-2023.html
+++ b/math-2023.html
@@ -118,7 +118,7 @@ <h1 id="title">PROPOSED Math Working Group Charter</h1>
               Chairs
             </th>
             <td>
-              Neil Soiffer (Talking Cat Software), Brain Kardell (Igalia)
+              Brain Kardell (Igalia), Neil Soiffer (Talking Cat Software)
             </td>
           </tr>
           <tr>
@@ -328,6 +328,7 @@ <h3>Timeline</h3>
               <li>August 2023: Implementation of MathML-to-speech/braille that makes use of accessibility annotations</li>
               <li>Sept 2023: First face-to-face meeting (TPAC)</li>
               <li>Mar 2024: PR, MathML Core</li>
+              <li>Sept 2024: Second face-to-face meeting (TPAC)</li>
               <li>Sept 2024: FPWD, MathML Core Level 2</li>
               <li>June 2024: PR MathML 4</li>
             </ul>
@@ -342,7 +343,7 @@ <h2>Success Criteria</h2>
 <li>There are independent, interoperable native implementations of MathML Core Level 1 that are widely used.</li>
 <li>The larger Web Platform ecosystem shows signs of movement toward creating and using new MathML content, including direct use of core features aimed at improving accessibility by authoring tools and MathML converters.</li>
 <li>There is proven advancement and interest by implementers in MathML Core Level 2, exploring linking, better alignment with how the larger Web Platform evolves (Shadow DOM, Custom Elements, CSS).</li>
-<li>A MathML Full (MathML 4) specification, based on Core.</li>
+<li>A MathML Full (MathML 4) specification, based on Core is published.</li>
 <li>Each specification contains a section detailing all known security and privacy implications for implementers, Web authors, and end users.</li>
 <li>There are significant testing plans, and all testable changes have tests.</li>
 <li>There is an AAM (Accessibility API Mapping) for MathML Core and there are considerations of the benefits and impacts, including ways specification features can be used to address them, and recommendations for maximizing accessibility in implementations.</li>