From 9062c5b798831bf2c68e38f66ed7c41550aa52b1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mat=C3=ADas=20Locatti?=
 <42481638+goldenx86@users.noreply.github.com>
Date: Wed, 9 Jun 2021 00:19:36 -0300
Subject: [PATCH] Update
 site/content/entry/yuzu-progress-report-may-2021/index.md

Co-authored-by: Ameer J <52414509+ameerj@users.noreply.github.com>
---
 site/content/entry/yuzu-progress-report-may-2021/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/content/entry/yuzu-progress-report-may-2021/index.md b/site/content/entry/yuzu-progress-report-may-2021/index.md
index 7cded293..b1fabca3 100644
--- a/site/content/entry/yuzu-progress-report-may-2021/index.md
+++ b/site/content/entry/yuzu-progress-report-may-2021/index.md
@@ -70,7 +70,7 @@ primarily in keeping critical required information closer to the CPU.
 [Rodrigo](https://github.com/ReinUsesLisp) implemented a new method (solving some issues with the old one) that 
 [allows yuzu to access all the available host memory](https://github.com/yuzu-emu/yuzu/pull/6367). 
 Up to 50% of the total system RAM is available to the GPU as host memory, or as Windows calls it in the Task Manager, GPU shared memory. 
-This change means that the GPU effectively has more RAM available to use in Vulkan, helping delay our sadly famous out-of-memory issues with this API.
+This change means that the GPU effectively has more RAM available to use in Vulkan, helping delay our sadly infamous out-of-memory issues with this API.
 
 For those that can’t wait, want to test an in-development partial solution, and have experience with git, 
 [Maide](https://github.com/Kelebek1) has been working on what can be called a [“light Reaper”](https://github.com/yuzu-emu/yuzu/pull/6378),