From 1aa083f2b9e866ad214a2f49503cad7fe9ee966f Mon Sep 17 00:00:00 2001
From: Honghoa <59675380+kurenaihana@users.noreply.github.com>
Date: Tue, 10 Aug 2021 13:27:19 -0300
Subject: [PATCH] Update index.md

---
 site/content/entry/yuzu-progress-report-jul-2021/index.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/site/content/entry/yuzu-progress-report-jul-2021/index.md b/site/content/entry/yuzu-progress-report-jul-2021/index.md
index a6136e4b..c08dae32 100644
--- a/site/content/entry/yuzu-progress-report-jul-2021/index.md
+++ b/site/content/entry/yuzu-progress-report-jul-2021/index.md
@@ -426,9 +426,9 @@ addressed on this PR.
 ## Technical Changes
 
 Meanwhile, [bunnei](https://github.com/bunnei) was busy [improving the management of kernel objects](https://github.com/yuzu-emu/yuzu/pull/6551), reducing drastically the 
-amount of objects that kept dangling on memory after closing the emulation session.
+amount of objects that kept dangling in memory after closing the emulation session.
 
-A dangling object refers to information that has references in memory (i.e. pointers to access it), even though the object isn't being used any more.
+A dangling object refers to a stale object in memory that still has references, even though the object is no longer in use.
 
 In yuzu, kernel objects are implemented so that they keep track of themselves through a [reference counter](https://en.wikipedia.org/wiki/Reference_counting), which keeps the 
 object alive for as long as they're needed.