rename "joypad" to "controller" in docs

docs/development/retroarch/input/parallel-port-controllers.md

@@ -1,8 +1,8 @@
-# Parallel port joypads
+# Parallel port controllers
 
-## Linux parport joypad driver
+## Linux parport controller driver
 
-RetroArch supports parallel port joypads on Linux via the "parport" joypad driver. It uses an extended version of the Linux Multisystem 2-button joystick protocol.
+RetroArch supports parallel port controllers on Linux via the "parport" controller driver. It uses an extended version of the Linux Multisystem 2-button joystick protocol.
 
 | Function | Pin | Register | Bit | Active |
 |----------|-----|----------|-----|--------|
@@ -24,4 +24,4 @@ RetroArch supports parallel port joypads on Linux via the "parport" joypad drive
 
 RetroArch does not perform debouncing, and so long as the button settling time is less than the frame time no bouncing will be observed. This replicates the latching behavior common in old games consoles. For optimum latency and jitter a high performance debouncing routine should be implemented in the controller hardware.
 
-Parallel port hardware does not provide a way to detect non-connected pins. To avoid rendering the menu usable with spurious button presses, RetroArch checks each pin on startup and assumes any active pin is not connected. Avoid holding joypad buttons while starting RetroArch or those buttons will be disabled.
+Parallel port hardware does not provide a way to detect non-connected pins. To avoid rendering the menu usable with spurious button presses, RetroArch checks each pin on startup and assumes any active pin is not connected. Avoid holding controller buttons while starting RetroArch or those buttons will be disabled.

docs/guides/cheat-codes.md

@@ -98,7 +98,7 @@ The "Value Increase Each Iteration" would normally be 0 in the above scenario bu
 RetroArch also has the ability to make your controller rumble when changes in the emulator/core memory occur.  It is based off of the same RetroArch-handled cheat codes described above.  For example, after
 finding the memory location for the number of lives in a game (via the cheat searching interface) you can set it up such that every time the value decreases (lose a life) the controller rumbles.
 
-Rumble tested with X360 controller, input driver dinput, joypad driver xinput.
+Rumble tested with X360 controller, input driver dinput, controller driver xinput.
 
 Available rumble controls:
 

docs/guides/rgui.md

@@ -43,7 +43,7 @@ By design, the config file is considered immutable as it is likely maintained by
 * To exit the menu, use F1 or `Resume Game`.
 * To start immediately in RGUI without any game or core loaded, use the `--menu` command line option. As a special case, if no arguments are received, it is treated the same as running `retroarch --menu`.
 
-Menu toggle button can be mapped to joypad as well, see option `input_menu_toggle` option in `retroarch.cfg`.
+Menu toggle button can be mapped to a controller as well, see option `input_menu_toggle` option in `retroarch.cfg`.
 
 ## Navigating the menu
 
@@ -114,8 +114,8 @@ Currently you can configure two settings per player (on PC):
 - **Device**: Picks which gamepad to use for player N. The name of the pad is available.
 - **Device Type**: Picks which device type to use. This is relevant for the libretro core itself, and mostly useful for PlayStation, which needs to know if you're using a DualAnalog device or not.
 
-### Configuring joypad input
-Configuring joypad input is supported from within RGUI.
+### Configuring controller input
+Configuring controller input is supported from within RGUI.
 Normal gameplay binds as well as RGUI hotkey binding is supported. It is possible to bind everything in succession for convenience.
 
 ### Configuring keyboard input