Deployed d6fca30 with MkDocs version: 1.5.3

Handling-Tickets/index.html

@@ -4644,14 +4644,19 @@ <h3 id="claiming-a-ticket">Claiming a Ticket<a class="headerlink" href="#claimin
 </ul>
 <h2 id="if-a-developer-becomes-active-again">If a Developer Becomes Active Again<a class="headerlink" href="#if-a-developer-becomes-active-again" title="Permanent link">link</a></h2>
 <p><em>Who handles tickets for achievements edited while the developer is Inactive?</em></p>
-<p>If an inactive developer becomes active again, they are still responsible for their achievements that have been fixed by other developers.
-* It is strongly recommended that the newly active dev review any tickets that were resolved during their inactivity period so they can understand the changes made to their achievements.
-* If necessary, reach out to the developer who made the updates that resolved the tickets.
-* If the newly active developer no longer wants to be the owner of the achievements, they can reach out to the Developer Compliance team to inquire about a reauthor of said achievements.
-  * Note that an accepted reauthor will be handled on a case-by-case basis, depending on the developers in question as well as the changes made to the achievements. This rule will be reevaluated if the implementation of a set or achievement maintainer is introduced.</p>
+<p>If an inactive developer becomes active again, they are still responsible for their achievements that have been fixed by other developers.</p>
+<ul>
+<li>It is strongly recommended that the newly active dev review any tickets that were resolved during their inactivity period so they can understand the changes made to their achievements.</li>
+<li>If necessary, reach out to the developer who made the updates that resolved the tickets.</li>
+<li>If the newly active developer no longer wants to be the owner of the achievements, they can reach out to the Developer Compliance team to inquire about a reauthor of said achievements.<ul>
+<li>Note that an accepted reauthor will be handled on a case-by-case basis, depending on the developers in question as well as the changes made to the achievements. This rule will be reevaluated if the implementation of a set or achievement maintainer is introduced.</li>
+</ul>
+</li>
+</ul>
 <h2 id="changelog">Changelog<a class="headerlink" href="#changelog" title="Permanent link">link</a></h2>
 <p>Last 10 changes on this page:</p>
 <ul>
+<li><code>[2024-03-11 14:11] Andrew Comer:</code> Updated Handling Tickets (markdown)</li>
 <li><code>[2024-03-11 14:08] Andrew Comer:</code> Updated Handling Tickets (markdown)</li>
 <li><code>[2024-03-11 14:03] Andrew Comer:</code> Bullet formatting fixes.</li>
 <li><code>[2024-03-11 13:57] Andrew Comer:</code> Bullet formatting fixes.</li>
@@ -4661,7 +4666,6 @@ <h2 id="changelog">Changelog<a class="headerlink" href="#changelog" title="Perma
 <li><code>[2024-01-13 23:04] The Mystical One:</code> Updated Handling Tickets (markdown)</li>
 <li><code>[2024-01-13 23:03] The Mystical One:</code> Updated Handling Tickets (markdown)</li>
 <li><code>[2024-01-13 22:57] The Mystical One:</code> Updated Handling Tickets (markdown)</li>
-<li><code>[2024-01-13 22:55] The Mystical One:</code> Changed the Set Claims &amp; Tickets heading to be a question so that it is much more eye-catching.</li>
 </ul>