diff --git a/Usage.md b/Usage.md
index 4c57d2f..fa6c9fb 100644
--- a/Usage.md
+++ b/Usage.md
@@ -14,12 +14,13 @@ At least one server needs to be defined. If the management server also is a KVM
 
 
 **VMs**
+
 The creation and editing of VMs should probably be quite self explanatory. Nevertheless, here are a few hints that didn't fit in the placeholder of the fields. :-)<br/>
-As soon as you choose the server, it scans the defined image and iso directories and created the dropdown menues. If you change anything, it might be woth to just change the server back and forth to get an updated dropdown.
-The VNC display is set as integer which represents the display numer, which in turn means that the vnc server will listern to port 5900 + $display. The same is true for the vnc-websocket. Set it as integer which will be added to 5700. This means we have a maximum of 200 websockets! If the weboscket is not set, no novnc link gets shown and the vm needs to get connected through a VNC client. Look out that you do not use a VNC or websocket port multiple times!
-Accessing NOVNC through https requires special setup. See the [[Installation]] page for details.
-Images need to get created manually for now via qemu-img (-f qcow2 imagename 20G) command.
+As soon as you choose the server, it scans the defined image and iso directories and created the dropdown menues. If you change anything, it might be woth to just change the server back and forth to get an updated dropdown.<br/>
+The VNC display is set as integer which represents the display numer, which in turn means that the vnc server will listern to port 5900 + $display. The same is true for the vnc-websocket. Set it as integer which will be added to 5700. This means we have a maximum of 200 websockets! If the weboscket is not set, no novnc link gets shown and the vm needs to get connected through a VNC client. Look out that you do not use a VNC or websocket port multiple times!<br/>
+Accessing NOVNC through https requires special setup. See the [[Installation]] page for details.<br/>
+Images need to get created manually for now via qemu-img (-f qcow2 imagename 20G) command.<br/>
 
-The shutdown command is sent through acpi to the guest VMs. Make sure that some daemon is running to listen on these events. After a few seconds, the VM gets killed automatically if the VM is still up!
+The shutdown command is sent through acpi to the guest VMs. Make sure that some daemon is running to listen on these events. After a few seconds, the VM gets killed automatically if the VM is still up!<br/>
 
-The autostart option gets set on the host during a cold-boot of the VM! So after toggling the option, a shutdown/start is needed to setup the needed startup scripts. As there are currently no init scripts / systemd unit, a cron entry is needed.... See the [[Installation]] page for details.
\ No newline at end of file
+The autostart option gets set on the host during a cold-boot of the VM! So after toggling the option, a shutdown/start is needed to setup the needed startup scripts. As there are currently no init scripts / systemd unit, a cron entry is needed.... See the [[Installation]] page for details.<br/>
\ No newline at end of file