From 42b56d23f4a2db8a2bd582923e6454c1e1bd8cbd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mat=C3=ADas=20Locatti?=
 <42481638+goldenx86@users.noreply.github.com>
Date: Sat, 3 Dec 2022 16:09:53 -0300
Subject: [PATCH] More byte

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

diff --git a/site/content/entry/yuzu-progress-report-nov-2022/index.md b/site/content/entry/yuzu-progress-report-nov-2022/index.md
index 01820571..3815f19b 100644
--- a/site/content/entry/yuzu-progress-report-nov-2022/index.md
+++ b/site/content/entry/yuzu-progress-report-nov-2022/index.md
@@ -76,7 +76,7 @@ We strongly recommend using a global setting of Auto CPU accuracy, and only impl
 Games WILL break with unsafe settings.
 
 Back on GPU related issues, AMD has its own share of issues, it always does.
-Users were quick to point out that the game looked like the usual cheap method USA films retort to when showing anything is happening south of their borders, with a yellow filter applied.
+Users were quick to point out that the game looked like the usual cheap method USA films resort to when showing anything happening south of their borders, with a yellow filter applied.
 This issue is for the history books, as both the official AMD drivers (the Windows driver, amdvlk and AMDGPU-PRO) *and* mesa (RADV) share the same behaviour.
 
 Let’s provide some context.