From 069dc1dbe6811ace34e9407ae6811325d7a5ea28 Mon Sep 17 00:00:00 2001
From: cyber-sushi <99445392+cyber-sushi@users.noreply.github.com>
Date: Fri, 1 Dec 2023 13:03:05 +0100
Subject: [PATCH] Updated comments

---
 config examples/config-stadia.toml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/config examples/config-stadia.toml b/config examples/config-stadia.toml
index 1182527..197361b 100644
--- a/config examples/config-stadia.toml	
+++ b/config examples/config-stadia.toml	
@@ -1,6 +1,6 @@
 #SAMPLE CONFIG FILE FOR GOOGLE STADIA CONTROLLERS
-#Put this in ~/.config/makima and rename it to config.toml
-#You can find the available keycodes in /usr/include/linux/input-event-codes.h
+#Put this in ~/.config/makima and rename it to the exact name of the device as shown by the 'evtest' command, including spaces and capitalization.
+#You can find all the available keycodes in /usr/include/linux/input-event-codes.h
 #If you're not sure which keycode corresponds to which key, you can run 'evtest', select your keyboard/mouse and press the corresponding key/button.
 #This config file is tested for Stadia controllers. When using a different controller, if no specific config file for your device is available, change the keycodes on the left according to those of your controller (evtest is your friend again). If your controller has a button to enable/disable analog sticks, make sure they're enabled.