From 28ba22e8ececa18b63c22d1478cd518e921ad7b5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mat=C3=ADas=20Locatti?=
 <42481638+goldenx86@users.noreply.github.com>
Date: Sat, 10 Feb 2024 18:56:43 -0300
Subject: [PATCH] Update
 site/content/entry/yuzu-progress-report-jan-2024/index.md

Co-authored-by: Schplee <24275329+Schplee@users.noreply.github.com>
---
 site/content/entry/yuzu-progress-report-jan-2024/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/content/entry/yuzu-progress-report-jan-2024/index.md b/site/content/entry/yuzu-progress-report-jan-2024/index.md
index e9e09c3e..7ed4ea2c 100644
--- a/site/content/entry/yuzu-progress-report-jan-2024/index.md
+++ b/site/content/entry/yuzu-progress-report-jan-2024/index.md
@@ -32,7 +32,7 @@ Implementing the requirements to support multiprocess in yuzu led us to make fiv
 
 ### Device mapping and SMMU
 
-We start off with a big on: Blinkhawk implemented device memory mapping emulation and rewrote the GPU implementation with support for the {{< gh-hovercard "12579" "SMMU," >}} or for desktop enthusiasts/Linux VM users/UEFI lurkers, its other common name, IOMMU.
+We start off with a big one: Blinkhawk implemented device memory mapping emulation and rewrote the GPU implementation with support for the {{< gh-hovercard "12579" "SMMU," >}} or for desktop enthusiasts/Linux VM users/UEFI lurkers, its other common name, IOMMU.
 
 The ARM **S**ystem **M**emory **M**anagement **U**nit handles memory mapping for peripheral devices like the GPU.
 It’s a hardware component on the Switch in charge of translating device virtual memory addresses into physical memory addresses.