diff --git a/inputmodule-control/src/inputmodule.rs b/inputmodule-control/src/inputmodule.rs
index 60c6c2e..2f26244 100644
--- a/inputmodule-control/src/inputmodule.rs
+++ b/inputmodule-control/src/inputmodule.rs
@@ -395,7 +395,7 @@ fn simple_cmd(serialdev: &str, command: Command, args: &[u8]) {
     match port_result {
         Ok(mut port) => simple_cmd_port(&mut port, command, args),
         Err(error) => match error.kind {
-            serialport::ErrorKind::Io(std::io::ErrorKind::PermissionDenied) => panic!("Permission denied, couldn't access input module port. Ensure that udev rule is installed or the port the module is on is otherwise accessible."),
+            serialport::ErrorKind::Io(std::io::ErrorKind::PermissionDenied) => panic!("Permission denied, couldn't access inputmodule serialport. Ensure that you have permission, for example using a udev rule or sudo."),
             other_error => panic!("Couldn't open port: {:?}", other_error)
         }
     };
diff --git a/ledmatrix/50-framework.rules b/ledmatrix/50-framework.rules
index b5c9e32..50524f3 100644
--- a/ledmatrix/50-framework.rules
+++ b/ledmatrix/50-framework.rules
@@ -1 +1,2 @@
-SUBSYSTEMS=="usb", ATTRS{idVendor}=="32ac", ATTRS{idProduct}=="0020", MODE:="0666"
\ No newline at end of file
+# Framework Laptop 16 - LED Matrix Inputmodule
+SUBSYSTEMS=="usb", ATTRS{idVendor}=="32ac", ATTRS{idProduct}=="0020", MODE:="0666"
diff --git a/ledmatrix/README.md b/ledmatrix/README.md
index 2eb4547..20343df 100644
--- a/ledmatrix/README.md
+++ b/ledmatrix/README.md
@@ -19,10 +19,10 @@ Connection to the host system is via USB 2.0 and currently there is a USB Serial
 
 To ensure that the input module's port is accessible, install the `udev` rule for it located in the `50-framework.rules` file.
 
-1. Copy it to your udev rules directory. On Ubuntu, this is located at `/etc/udev/rules.d/`
-2. Reload the rules with `sudo udevadm control --reload`
+1. Copy it to your udev rules directory, which is usually at: `/etc/udev/rules.d/`
+2. Reload and apply the rules with `sudo udevadm control --reload && sudo udevadm trigger`
 
-You can debug issues using the `udevadm monitor --environment` command. Ensure that the device's `idVendor` and `idProduct` match when you plug in the device.
+You can debug issues using the `udevadm monitor --environment` command.
 
 ## Controlling