From 6cc1ec4382ddb43f1ed8c32c9aad235228402d57 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:19:36 -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 724057be..71a8828b 100644
--- a/site/content/entry/yuzu-progress-report-may-2021/index.md
+++ b/site/content/entry/yuzu-progress-report-may-2021/index.md
@@ -59,7 +59,7 @@ The readings were previously accurate when the GPU thread was synchronous with t
 Now that asynchronous GPU emulation is implemented, this is no longer the case.
 
 The solution epicboy came up with is, instead of letting the nvflinger service handle the counter, [let the graphics API inform the counter after it finishes drawing the frame](https://github.com/yuzu-emu/yuzu/pull/6317).
-this way the value is far more accurate and stable on performance oscillations.
+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, giving more information on the reading.
 
 A big one for Vulkan users waiting for `Project Reaper`to leave the development board.