Update README.md

Author: sincze

README.md

@@ -291,18 +291,20 @@ Serial Port to be setup as `9600 baud, 8 bit, no partity, 1 stop bit`. Must be s
 Additional expected similar solutions could be constructed from USR-TCP232-306, USR-TCP232-304 connected directly to the control panel or
 USR-TCP232-302 conected to an existing JA-80T serial cable.
 
-Another solution for remote usage could be via the use of USBIP that needs to be installed on the server (jablotron alarm side) and the client (homeassistant running this repo.)
+Another solution for remote usage could be via the use of a tool called ```usbip``` that needs to be installed on the server **(jablotron alarm side)** and the client **(homeassistant running this repo.)**
 
-Using the following command on the server to check if (in this case JA-82T) is visible:
+First using the following command ```dmesg | grep hid``` on the **server** to check if (in this case JA-82T) is visible:
 ```
-dmesg | grep hid
-
 [8740307.349070] hid-generic 0003:16D6:0007.0002: hiddev96,hidraw0: USB HID v1.11 Device [JABLOTRON ALARMS JA-82T PC Interface] on usb-0000:01:00.0-1.3/input0
 ```
-Now we know the device we are looking for is hidraw0 and the ID **16D6:0007** the id can also be optained if the command ```lsusb``` is executed
+Now we know the device we are looking for is hidraw0 and the ID **16D6:0007**, by the way the ID can also be optained if the command ```lsusb``` is executed
+```
+Bus 001 Device 013: ID 16d6:0007 JABLOCOM s.r.o. JA-82T PC Interface
+```
+
+As stated installation of usbip needs to be done on the **Server** and **CLient**
 
-Installation of usbip needs to be done on the **CLient** and **Server** via:
-After the above command on the Server execute:
+Server:
 ```
 sudo apt install usbip hwdata usbutils
 modprobe usbip_host
@@ -326,28 +328,29 @@ ExecStop=/bin/sh -c "/usr/sbin/usbip unbind --$(/usr/sbin/usbip list -p -l | gre
 
 [Install]
 WantedBy=multi-user.target
+
 ```
 Only change the #usbid=16d6:0007# if necessary.
 Save the file and execute:
-
 ```
 # reload systemd, enable, then start the service
 sudo systemctl --system daemon-reload
 sudo systemctl enable usbipd.service
 sudo systemctl start usbipd.service
 ```
 The server setup is now complete, move over to the client
+
+Client:
 ```
 sudo apt install usbip hwdata usbutils
 modprobe vhci-hcd
 echo 'vhci-hcd' >> /etc/modules
-```
-Much like we did on the server, we’re going to need to modify the ExecStart and ExecStop lines below to search for the correct USB device ID that’s being presented by your USB/IP server. Likewise, change the IP 192.168.0.10 to match your USB server.
 
-```
+# Create a systemd service
 nano /lib/systemd/system/usbip.service
 ```
 
+Much like we did on the server, we’re going to need to modify the ExecStart and ExecStop lines below to search for the correct USB device ID that’s being presented by your USB/IP server. Likewise, change the IP 192.168.0.10 to match your server.
 ```
 [Unit]
 Description=usbip client
@@ -361,8 +364,8 @@ ExecStop=/bin/sh -c "/usr/sbin/usbip detach --port=$(/usr/sbin/usbip port | grep
 
 [Install]
 WantedBy=multi-user.target
-
 ```
+
 Save that file, then run the following commands in your shell:
 
 ```
@@ -381,7 +384,6 @@ For Docker users we need to add the following to the docker_compose file to enab
     devices:
       - /dev/hidraw0
 
-
 ## Troubleshooting
 
 Additional logging can be enabled in configuration.yaml