diff --git a/getting_started.md b/getting_started.md
index 86f2d9b..b413a57 100644
--- a/getting_started.md
+++ b/getting_started.md
@@ -188,6 +188,14 @@ With **officially supported controllers**, the mapping is:
 
 Unsupported USB controllers might still work, but the default mapping might be wonky.
 
+## Custom Gamepad Mapping
+
+You can also create your own USB Gamepad mapping so suit your exact needs.
+
+You can even have it **control mouse and keyboard**, in order to play games that did not have native gamepad support!
+
+[Download the configurator](https://github.com/dekuNukem/usb4vc-configurator/blob/master/README.md) and follow the instruction to set it up.
+
 ## Joycheck DOS Program
 
 You can [download this DOS program](https://github.com/dekuNukem/USB4VC/raw/master/resources/joytest.zip) to visualize what the gamepad is doing, great for troubleshooting! Found on this [vogons thread](https://www.vogons.org/viewtopic.php?p=187168#p187168).
@@ -198,14 +206,6 @@ You can [download this DOS program](https://github.com/dekuNukem/USB4VC/raw/mast
 
 ![Alt text](photos/joycheck.png)
 
-## Custom Gamepad Mapping
-
-You can also create your own USB Gamepad mapping so suit your exact needs.
-
-You can even have it **control mouse and keyboard**, in order to play games that did not have native gamepad support!
-
-[Download the configurator](https://github.com/dekuNukem/usb4vc-configurator/blob/master/README.md) and follow the instruction to set it up.
-
 ## Software Updates
 
 Connect RPi to internet. You can [set up WiFi](#optional-set-up-wifi), or plug in an Ethernet cable.
diff --git a/technical_notes.md b/technical_notes.md
index f9751d4..0595d83 100644
--- a/technical_notes.md
+++ b/technical_notes.md
@@ -54,10 +54,20 @@ event0  event1  event2  mice  mouse0  mouse1
 
 * [Here's a good article](https://thehackerdiary.wordpress.com/2017/04/21/exploring-devinput-1/) that goes into a bit more details.
 
-* You can use `evtest` to see input events in real time.
-
 * USB4VC reads those events from all input devices, processes them, and send them out to the Protocol Card.
 
+* To see it in action, you can select `Show Event Codes` from the main menu:
+
+![Alt text](photos/showev.jpeg)
+
+* It will show a summary of latest input events, including device name, USB vendor and product ID, and event code name and value.
+
+![Alt text](photos/evexample.jpeg)
+
+* To exit, **HOLD DOWN** `+` button during an input event.
+
+* You can also `ssh` into it and use `evtest` to see more detailed reports.
+
 ## Hardware Pinout
 
 The Protocol Card connector directly maps to the Raspberry Pi Header, although the pins are flipped around.