diff --git a/readme/usage.md b/readme/usage.md
index 6bb47577..24170668 100644
--- a/readme/usage.md
+++ b/readme/usage.md
@@ -5,12 +5,23 @@ and search for 'Key Mapper'. You should be prompted for your sudo password
as special permissions are needed to read events from `/dev/input/` files.
You can also start it via `sudo key-mapper-gtk`.
+
+
+
+
+
+Hitting a key on the device that is selected in the large dropdown on the top
+should display the key on the bottom of the window, and write it into the selected
+row (as shown in the screenshots).
+
+For changes to take effect, save the preset first. Otherwise, the daemon
+won't be able to know about your changes. Afterwards press the "Apply" button.
+
To change the mapping, you need to use the "Apply Defaults" button, so that
the application can read the original keycode. It would otherwise be
invisible since the daemon maps it independently of the GUI.
-For changes to take effect, save the preset first. Otherwise, the daemon
-won't be able to know about your changes.
+## Troubleshooting
If stuff doesn't work, check the output of `sudo key-mapper-gtk -d` and feel free
to [open up an issue here](https://github.com/sezanzeb/key-mapper/issues/new).
diff --git a/readme/usage_1.png b/readme/usage_1.png
new file mode 100644
index 00000000..9f68e6e2
Binary files /dev/null and b/readme/usage_1.png differ
diff --git a/readme/usage_2.png b/readme/usage_2.png
new file mode 100644
index 00000000..044ad3c4
Binary files /dev/null and b/readme/usage_2.png differ