From bd7f9e73254b05ed105598ac2637b9e96b82160f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mat=C3=ADas=20Locatti?=
 <42481638+goldenx86@users.noreply.github.com>
Date: Sat, 16 Dec 2023 00:07:51 -0300
Subject: [PATCH] Update index.md

---
 site/content/entry/yuzu-progress-report-nov-2023/index.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/site/content/entry/yuzu-progress-report-nov-2023/index.md b/site/content/entry/yuzu-progress-report-nov-2023/index.md
index 4e9b45f9..5f97175b 100644
--- a/site/content/entry/yuzu-progress-report-nov-2023/index.md
+++ b/site/content/entry/yuzu-progress-report-nov-2023/index.md
@@ -308,8 +308,8 @@ Fixing this blockade fixes shutdown operations on Android.
 
 Next one is quite a bit more involved, as it involves the procedure needed to ~~kill~~ terminate a process, James Bond style.
 This procedure consists of two steps for each thread in the terminated process:
-- - The thread is marked for termination, and an interrupt is sent to all cores with that thread's affinity if it is runnable.
-- - The kernel then waits for the thread to actually terminate.
+- The thread is marked for termination, and an interrupt is sent to all cores with that thread's affinity if it is runnable.
+- The kernel then waits for the thread to actually terminate.
 
 Runnable threads marked for termination are not removed from the scheduling priority queue. This means they can get scheduled during termination, even if the core already cleared the interrupt when a previous thread was terminated.
 {{< gh-hovercard "12025" "Checking for termination" >}} just before running the thread again, as the Switch does, fixed a very common shutdown deadlock on Android.