From d1dc440c22e8a604a84e62b29953b53beb6ad382 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Mat=C3=ADas=20Locatti?=
 <42481638+goldenx86@users.noreply.github.com>
Date: Sat, 9 Sep 2023 13:46:03 -0300
Subject: [PATCH] Update index.md

---
 site/content/entry/yuzu-progress-report-aug-2023/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/site/content/entry/yuzu-progress-report-aug-2023/index.md b/site/content/entry/yuzu-progress-report-aug-2023/index.md
index 74d945df..1a438b95 100644
--- a/site/content/entry/yuzu-progress-report-aug-2023/index.md
+++ b/site/content/entry/yuzu-progress-report-aug-2023/index.md
@@ -471,7 +471,7 @@ Feel free to experiment, and save your best gameplay moments!
   >}}
 
 Per-game settings are a great way to customise the settings and mods of each game.
-One option there that was in a weird spot was `Console mode` -- docked or handheld mode.
+One option in a weird spot was `Console mode` -- docked or handheld mode.
 The old implementation relied on controller profiles: the user would set some controller mapping, the type of controller, the console mode, save all of this as a profile, and then set each game to use the preferred controller profile.
 The problem with this approach is that it forces users to save different controller profiles, when in most cases a single one is used, for example, a Pro Controller profile using a Sony Dual Sense.
 To simplify this particular situation, toastUnlimited {{< gh-hovercard "11356" "added a Console Mode to the per-game system properties." >}} Much easier, right?