From acc6a3bdf5512ea23e6610d3870ef92a030b5b76 Mon Sep 17 00:00:00 2001
From: bicarus <202771338+bicarus-dev@users.noreply.github.com>
Date: Tue, 17 Feb 2026 16:15:45 -0800
Subject: [PATCH] Updated PC optimization (markdown)

---
 PC-optimization.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/PC-optimization.md b/PC-optimization.md
index 6c52922..8eb7298 100644
--- a/PC-optimization.md
+++ b/PC-optimization.md
@@ -19,7 +19,7 @@
 * Press F12 to see the FPS counter, confirm that it's what you expect. Also check your monitor (if not, check `log.txt`) to see that the game launched at the correct refresh rate. You want those numbers to match (60FPS and 60Hz, 120FPS and 120Hz).
   * Avoid using patches that run at refresh rates not originally intended by the game engine, as it may result in graphical glitches or overlapping sound effects.
   * In menus, your framerate will swing wildly, and this is perfectly normal, as the games aren't perfectly optimized for menus. Check for FPS only during gameplay.
-* Do not, under any circumstances, use "skip monitor check" or "shorten monitor check" patches. You might be asking, "why does the hex edit exist if you're not supposed to use it?" - the answer it that those were added for tools and EA server developers to boot the games quicker. If you're actually playing the game, you should keep monitor check.
+* Do not, under any circumstances, use "skip monitor check" patches. You might be asking, "why does the hex edit exist if you're not supposed to use it?" - the answer it that those were added for tools and EA server developers to boot the games quicker. If you're actually playing the game, you should keep monitor check.
 * It's OK if monitor checks aren't exactly 60.000Hz or 120.000Hz - because they're not like that at the arcade either. For example, IIDX LM cabs stabilize around 119.98xx.
   * Your monitor may boot into 59.94Hz or 119.2Hz (for example). This is OK for most games, as monitor check will eventually stabilize to match your refresh rate.