diff --git a/_conferences/2024/call.html b/_conferences/2024/call.html
index cc85258e..3384f425 100644
--- a/_conferences/2024/call.html
+++ b/_conferences/2024/call.html
@@ -136,68 +136,77 @@ <h4 id="submissions">Submissions</h4>
   </p>
   <p></p>
   <ul>
-    <li><strong>Long papers:</strong> abstract 2-4 pages (1000-2000 words).</li>
-    <p>
-      Long papers are expected to present overviews or detail specific aspects
-      of ongoing or completed projects, detailed case-studies or elaborated
-      perspectives on best practices in the field, or provide other reports on
-      topics relevant to the conference.
-    </p>
-    <p>
-      Speakers will be given 30 minutes each: 20 minutes for presentation, 10
-      minutes for discussion.
-    </p>
-    <li><strong>Short papers:</strong> abstract 1-2 pages (500-1000 words).</li>
-    <p>
-      Short papers are suitable for introducing tools, new ideas and
-      experimental topics.
-    </p>
-    <p>
-      Speakers will be given 15 minutes each: 10 minutes for presentation, 5
-      minutes for discussion.
-    </p>
-    <li><strong>Panels:</strong> 2-4 pages (1000-2000 words).</li>
-    <p>
-      Panels are suited to coordinated approaches or discussions relating to a
-      single theme. Submissions should describe the topic and nature of the
-      panel, along with the main theses and objectives of the proposed
-      contributions. Panel sessions will be given 90 minutes, which can be used
-      flexibly to include, for example, 3 individual papers followed by
-      questions, or a roundtable discussion.
-    </p>
-    <li><strong>Posters:</strong> 1-2 pages (500-1000 words).</li>
-    <p>
-      Posters are expected to report on early-stage work, introduce new work,
-      projects, or software, or present experimental ideas for community
-      feedback. A “poster slam” session will be dedicated to poster
-      presentations of 1 minute each. Subsequently, poster presenters will have
-      the chance to tell interested parties more about their project during the
-      poster exhibition, where the audience can browse freely.
-    </p>
+    <li>
+      <strong>Long papers:</strong> abstract 2-4 pages (1000-2000 words).
+      <p>
+        Long papers are expected to present overviews or detail specific aspects
+        of ongoing or completed projects, detailed case-studies or elaborated
+        perspectives on best practices in the field, or provide other reports on
+        topics relevant to the conference.
+      </p>
+      <p>
+        Speakers will be given 30 minutes each: 20 minutes for presentation, 10
+        minutes for discussion.
+      </p>
+    </li>
+    <li>
+      <strong>Short papers:</strong> abstract 1-2 pages (500-1000 words).
+      <p>
+        Short papers are suitable for introducing tools, new ideas and
+        experimental topics.
+      </p>
+      <p>
+        Speakers will be given 15 minutes each: 10 minutes for presentation, 5
+        minutes for discussion.
+      </p>
+    </li>
+    <li>
+      <strong>Panels:</strong> 2-4 pages (1000-2000 words).
+      <p>
+        Panels are suited to coordinated approaches or discussions relating to a
+        single theme. Submissions should describe the topic and nature of the
+        panel, along with the main theses and objectives of the proposed
+        contributions. Panel sessions will be given 90 minutes, which can be
+        used flexibly to include, for example, 3 individual papers followed by
+        questions, or a roundtable discussion.
+      </p>
+    </li>
+    <li>
+      <strong>Posters:</strong> 1-2 pages (500-1000 words).
+      <p>
+        Posters are expected to report on early-stage work, introduce new work,
+        projects, or software, or present experimental ideas for community
+        feedback. A “poster slam” session will be dedicated to poster
+        presentations of 1 minute each. Subsequently, poster presenters will
+        have the chance to tell interested parties more about their project
+        during the poster exhibition, where the audience can browse freely.
+      </p>
+    </li>
     <li>
       <strong>Half- or full-day workshops:</strong> 2-3 pages (1000-1500 words).
+      <p>
+        Proposals must include conveners, a description of the workshop’s
+        objective and proposed duration, as well as its logistical and technical
+        requirements. Proposals must include:
+      </p>
+      <ul>
+        <li>
+          A brief outline of the proposed topic and its appeal to either the
+          text or music encoding communities, or both
+        </li>
+        <li>
+          The duration of the proposed workshop or seminar (half day, full day)
+        </li>
+        <li>
+          Any special requirements (e.g., participant-supplied laptops,
+          projector, flipchart)
+        </li>
+        <li>
+          A list of proposed workshop leader(s) with a brief biography of each
+          one
+        </li>
+      </ul>
     </li>
-    <p>
-      Proposals must include conveners, a description of the workshop’s
-      objective and proposed duration, as well as its logistical and technical
-      requirements. Proposals must include:
-    </p>
-    <ul>
-      <li>
-        A brief outline of the proposed topic and its appeal to either the text
-        or music encoding communities, or both
-      </li>
-      <li>
-        The duration of the proposed workshop or seminar (half day, full day)
-      </li>
-      <li>
-        Any special requirements (e.g., participant-supplied laptops, projector,
-        flipchart)
-      </li>
-      <li>
-        A list of proposed workshop leader(s) with a brief biography of each one
-      </li>
-    </ul>
   </ul>
 
   <p>