From c93869e056a7959418e24436ef5dcc57a496d686 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:18:11 -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 0ca2ccce..f43cf457 100644
--- a/site/content/entry/yuzu-progress-report-may-2021/index.md
+++ b/site/content/entry/yuzu-progress-report-may-2021/index.md
@@ -40,7 +40,7 @@ This can be partially solved by using High GPU accuracy in OpenGL with Assembly
 
 Textures blits (bit block transfers, a combination of bitmaps) can sometimes work out of bounds by design, by interleaving copy regions.
 yuzu has to be able to [understand this behaviour](https://github.com/yuzu-emu/yuzu/pull/6289) and return the correct portion, 
-something epicboy had no problem in properly implementing for us.
+something epicboy had no problem properly implementing for us.
 
 {{< imgs
 	"./blits.png| Here’s a beautifully detailed example of the old out-of-bounds wrong behaviour in red, and the correct result in blue, with the affected area moving to the next row,as it should"