From 91335587ed711d43fe7e744babfec4fa518715f0 Mon Sep 17 00:00:00 2001
From: Honghoa <59675380+kurenaihana@users.noreply.github.com>
Date: Fri, 11 Feb 2022 12:49:34 -0300
Subject: [PATCH] Update index.md

---
 site/content/entry/yuzu-progress-report-jan-2022/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/content/entry/yuzu-progress-report-jan-2022/index.md b/site/content/entry/yuzu-progress-report-jan-2022/index.md
index d92a2e74..ed6f0107 100644
--- a/site/content/entry/yuzu-progress-report-jan-2022/index.md
+++ b/site/content/entry/yuzu-progress-report-jan-2022/index.md
@@ -198,7 +198,7 @@ Another long-standing problem with `Pokémon Sword/Shield` was related to the co
 
 When a game requests certain services, instead of emulating the internal logic of the Nintendo Switch's OS (which would be Low-Level Emulation, `LLE`), yuzu runs an implementation written by the developers that performs the same job on the user's computer.
 
-The of these `HLE` services need to be able to interact with the emulated kernel, in order to grab locks and triggers for rescheduling, etc.
+These `HLE` services need to be able to interact with the emulated kernel, in order to grab locks and triggers for rescheduling, etc.
 yuzu achieves this by making use of `dummy threads`, which are created as an emulated `KThread` entity.
 
 A `dummy thread` is created for every thread of a service interface running in the user's computer (also called `host thread`), so that whenever the kernel needs to interact with a `host thread`, it can do so through these `dummy threads`.