Update faq.md

pages/faq.md

@@ -7,13 +7,13 @@ As a first step we recommend carefully reading our documentation on [GitHub](htt
 <details>
   <summary><b>Can I connect multiple servers to a single Pi-KVM?</b></summary>
 
-Yes, but it will require additional work to set up. See [this page](multiport.md).
+* Yes, but it will require additional work to set up. See [this page](multiport.md).
 </details>
 
 <details>
   <summary><b>Can I use Pi-KVM with non-Raspberry Pi boards?</b></summary>
 
-Yes, but you will have to prepare the operating system yourself. As for the Pi-KVM software, you will need to replace some config files (such as UDEV rules). If you are a developer or an experienced system administrator, you will not have any problems with this. In addition, we are open to patches. If you need help with this, please contact us via [Discord](https://discord.gg/bpmXfz5).
+* Yes, but you will have to prepare the operating system yourself. As for the Pi-KVM software, you will need to replace some config files (such as UDEV rules). If you are a developer or an experienced system administrator, you will not have any problems with this. In addition, we are open to patches. If you need help with this, please contact us via [Discord](https://discord.gg/bpmXfz5).
 </details>
 
 -----
@@ -22,7 +22,9 @@ Yes, but you will have to prepare the operating system yourself. As for the Pi-K
 <details>
   <summary><b>Where is the Pi-KVM configuration located?</b></summary>
 
-Almost all KVMD (the main daemon controlling Pi-KVM) configuration files located in `/etc/kvmd`. You can also find nginx configs and SSL certificates there. KVMD configs use [YAML](config.md) syntax. The specific platform parameters can be found in the file `/etc/kvmd/main.yaml` and **you should never edit it**. Use `/etc/kvmd/override.yaml` to redefine the system parameters. Another files that are also not recommended for editing have read-only permissions. If you edit any of these files, you will need to manually make changes to them when you upgrade your system. You can view the current configuration and all available KVMD parameters using the command `kvmd -m`.
+* Almost all KVMD (the main daemon controlling Pi-KVM) configuration files located in `/etc/kvmd`. You can also find nginx configs and SSL certificates there. KVMD configs use [YAML](config.md) syntax. The specific platform parameters can be found in the file `/etc/kvmd/main.yaml` and **you should never edit it**. Use `/etc/kvmd/override.yaml` to redefine the system parameters.
+  
+  Another files that are also not recommended for editing have read-only permissions. If you edit any of these files, you will need to manually make changes to them when you upgrade your system. You can view the current configuration and all available KVMD parameters using the command `kvmd -m`.
 </details>
 
 <details>
@@ -34,11 +36,12 @@ The Pi-KVM file system is always mounted in read-only mode. This measure prevent
 <details>
   <summary><b>How do I update Pi-KVM with the latest software?</b></summary>
 
-Pi-KVM OS is based on Arch Linux ARM and is fully updated from the repository by a regular package manager. Connect to your Pi-KVM via ssh and run:
-```
-rw
-pacman -Syu
-reboot
-```
-:exclamation: Pacman saves all installed packages in a compressed format so that you can roll back to the old version if something goes wrong. After you've updated and made sure everything works, it makes sense to clear the package cache so that it doesn't take up space on the SD card: `rw; rm -rf /var/cache/pacman/pkg; ro`.
+  Pi-KVM OS is based on Arch Linux ARM and is fully updated from the repository by a regular package manager. Connect to your Pi-KVM via ssh and run:
+  ```
+  rw
+  pacman -Syu
+  reboot
+  ```
+  
+  :exclamation: Pacman saves all installed packages in a compressed format so that you can roll back to the old version if something goes wrong. After you've updated and made sure everything works, it makes sense to clear the package cache so that it doesn't take up space on the SD card: `rw; rm -rf /var/cache/pacman/pkg; ro`.
 </details>