From 8a2a34d7a8e2f7debcac513d89b2001c8a637bcc Mon Sep 17 00:00:00 2001
From: ExpoSeed <43502820+ExpoSeed@users.noreply.github.com>
Date: Tue, 26 Jan 2021 14:24:24 -0600
Subject: [PATCH] Updated Improving the WaitForVBlank function (markdown)

---
 Improving-the-WaitForVBlank-function.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Improving-the-WaitForVBlank-function.md b/Improving-the-WaitForVBlank-function.md
index ef28091..d35eca9 100644
--- a/Improving-the-WaitForVBlank-function.md
+++ b/Improving-the-WaitForVBlank-function.md
@@ -8,7 +8,7 @@ In Emerald, Gamefreak used a `while` loop that kept on checking for VBlank over
 
 The correct way to vsync is to use a [software interrupt/BIOS call](https://www.coranac.com/tonc/text/swi.htm#sec-vsync2). In short, we put the CPU in low power mode while we wait for the next VBlank, and on the next VBlank the CPU comes back to life.
 
-The easiest way to do so, is by copying and pasting the function directly from Ruby and Sapphire, which means modifying the function like this:
+The easiest way to do so, is by copying and pasting the function directly from Ruby and Sapphire, which means modifying the function in `src/main.c` like this:
 
 ```diff
 static void WaitForVBlank(void)