diff --git a/README b/README.md
similarity index 91%
rename from README
rename to README.md
index ba72580..da44dcd 100644
--- a/README
+++ b/README.md
@@ -1,7 +1,8 @@
 # UPower
 
 Requirements:
-```
+
+```text
   glib-2.0             >= 2.66.0
   gio-2.0              >= 2.16.1
   gudev-1.0            >= 235    (Linux)
@@ -17,32 +18,36 @@ org.freedesktop.UPower service via the system message bus.
 ## Debugging
 
 When doing bug reports, the following information can be useful:
-- `grep . /sys/class/power_supply/*/*`:
+
+- `grep . /sys/class/power_supply/*/*`  
   This includes the current kernel view of all power supplies in the
   system. It is always a good idea to include this information.
-- `udevadm info -e`:
+- `udevadm info -e`  
   This shows the hardware configuration and is relevant when e.g. the
   type of an external device is misdetected.
-- `upower -d`:
+- `upower -d`  
   Shows upower's view of the state
-- `upower --monitor-detail`:
+- `upower --monitor-detail`  
   Dumps device information every time that a change happens. This helps
   with debugging dynamic issues.
-- `udevadm monitor`:
+- `udevadm monitor`  
   Dumps the udev/kernel reported hardware changes (and addition/removal).
   This is helpful when debugging dynamic issues, in particular if it is
   not clear whether the issue is coming from the kernel or upower.
 
 In addition, it can also be useful to run upower in debug mode and post the
 logs. There are two ways of doing so:
+
 - Run upower daemon manually, you can do so using:
   `sudo /usr/libexec/upowerd -rd`
 - Modify the systemd service and restart. This is best done by:
   1. `sudo systemctl edit upower.service`
   2. Adding the two lines:
-      ```
+
+      ```text
       [Service]
       Environment=G_MESSAGES_DEBUG=all
       ```
+
   3. `sudo systemctl restart upower.service`
   4. Grab logs using `journalctl -u upower.service` or similar