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 71a8828b..41afb491 100644
--- a/site/content/entry/yuzu-progress-report-may-2021/index.md
+++ b/site/content/entry/yuzu-progress-report-may-2021/index.md
@@ -60,7 +60,7 @@ 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.
-Additionally, the update frequency of the counter was changed from 2000 ms to 500 ms, giving more information on the reading.
+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. 
 The previous Vulkan `memory allocator` used local memory as top priority (that’s the physical VRAM on your dedicated GPU),