Update controller-autoconfiguration.md (#1072)

* Update controller-autoconfiguration.md

Add input_menu_toggle_btn_label, and input_screenshot_btn_label, to the "Add hotkey(s)" section

* Update controller-autoconfiguration.md

Explain how to apply hotkey button labels

* Update controller-autoconfiguration.md

Improved step 5 in the "Add hotkey(s)" section

Author: davidhedlund

docs/guides/controller-autoconfiguration.md

@@ -285,31 +285,40 @@ When using RetroArch, not all controller buttons are automatically mapped throug
 1. Identify special buttons on your controller
   - Look for buttons on your physical controller not automatically mapped by Retroarch.
   - Examples include
-    - *Menu Toggle* (virtually all controllers has them)
-    - Additional special buttons may be found on some controllers. For example, the *Capture* (screenshot) button and the *HOME* button on the Nintendo Switch Pro Controller are examples of such special buttons.
-2. Assign hotkeys in Retroarch
+    - *Menu Toggle* (virtually all controllers have them)
+    - Additional special buttons may be found on some controllers. For example, the *Capture* (screenshot) and the "Home" button on Nintendo Switch Pro Controller.
+3. Assign hotkeys in Retroarch
   - Launch Retroarch.
   - Navigate to: `Settings` → `Input` → `Hotkeys`.
   - Select the special function you want to assign (e.g., *Menu Toggle*, *Screenshot*).
   - Press the desired button on your controller to bind it.
   - Exit Retroarch properly to save the settings:
     - On most platforms, just closing Retroarch saves the config.
-    - On Android, explicitly quit via `Main Menu` → `Quit` to ensure save.
+    - On Android, explicitly quit via `Main Menu` → `Quit` to ensure settings are saved.
 
-3. Transfer hotkey assignments to your controller autoconfig file
+4. Transfer hotkey assignments to your controller autoconfig file
   - Open your main `retroarch.cfg` file.
-  - Locate the hotkey assignment lines, for example:
+  - Find and copy the hotkey assignment lines, for example:
     ```
-    input_menu_toggle_btn = "[x]"
-    input_screenshot_btn = "[y]"
+    input_menu_toggle_btn = "[w]"
+    input_screenshot_btn = "[x]"
     ```
-    (The values `[x]`, `[y]` are placeholders from your config.)
+    *(Replace `[w]` and `[x]` with your actual button values.)*
   - Open your controller’s autoconfig file, typically found at:
     ```
     retroarch/autoconfig/[platform]/[controller-name].cfg
     ```
-  - Append the copied hotkey lines to the bottom of this autoconfig file.
-  - Save the autoconfig file.
+  - Append the copied hotkey lines to the bottom of the autoconfig file.
+5. Add labels. They will be visible in `Settings` → `Input` → `Hotkeys`.
+  - Add variable names. Complement the variables that you just added to the autoconfig file with the corresponding label variables ([variable name]+"_label") at the absolute bottom of the file, for example:
+    ```
+    input_menu_toggle_btn_label = "[y]"
+    input_screenshot_btn_label = "[z]"
+    ```
+    *(Replace `[y]` and `[z]` with the appropriate label values described below.)*
+  - Add the corresponding variable label values. Refer to the manufacturer’s official labeling for each button, but avoid using all capital letters unless the name is an abbreviation. Use standard capitalization with an initial capital letter to improve readability. Also, do not add the word “button” if it is already part of the official name. For instance, Nintendo refers to the “HOME button” on the Switch Pro Controller, but you should label it simply as “Home.” Similarly, the menu toggle label for Sony PlayStation controllers is “PS.” This approach balances clarity and respect for official naming.
+6. Save the autoconfig file.
+7. Restart RetroArch and navigate to `Settings` → `Input` → `Hotkeys` to confirm that they look as intended.
 
 ### Analog L2/R2 remapping
 RetroArch has a bug([ref1](https://github.com/libretro/RetroArch/issues/6920), [ref2](https://github.com/libretro/RetroArch/issues/16767)) that causes analog L2/R2 triggers to be incorrectly mapped as digital buttons instead of analog axes when configuring controls through the UI. This affects pressure-sensitive triggers on controllers like PlayStation 2 and later, making some games unplayable due to the lack of analog input.