From dc2dbbba890a41b3dbe5cf0f65c46cb8fa0aaea6 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 09:21:07 -0300
Subject: [PATCH] Update
 site/content/entry/yuzu-progress-report-may-2021/index.md

Co-authored-by: Schplee <24275329+Schplee@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 41afb491..706f0990 100644
--- a/site/content/entry/yuzu-progress-report-may-2021/index.md
+++ b/site/content/entry/yuzu-progress-report-may-2021/index.md
@@ -62,7 +62,7 @@ The solution epicboy came up with is, instead of letting the nvflinger service h
 This way, the value is far more accurate and stable on performance oscillations.
 Additionally, the update frequency of the counter was changed from 2000 ms to 500 ms to allow for more frequent and up-to-date information to be displayed.
 
-A big one for Vulkan users waiting for `Project Reaper`to leave the development board. 
+And now for a big update for Vulkan users waiting for `Project Reaper` to leave the development board. 
 The previous Vulkan `memory allocator` used local memory as top priority (that’s the physical VRAM on your dedicated GPU), 
 and only used host memory in certain applicable cases that varied depending on how the GPU driver informed the different memory heaps available to yuzu, 
 primarily in keeping critical required information closer to the CPU.