update

docs/vnc.md

@@ -30,9 +30,10 @@ than the browser, especially on weak client computers.
 
 3. ??? tip "Optional for *non-TigerVNC* clients: Change the keybobard layout for non-US keyboard"
 
-        Some clients does not support direct keyboard access. 
+        This step is nessessory if you're using a client that does not support
+        the direct keyboard access.
 
-        Edit the file `/etc/kvmd/override.yaml` and add your layout for the client:
+        In this case you can force the client layout in `/etc/kvmd/override.yaml`:
 
         ```yaml
         vnc:
@@ -45,10 +46,10 @@ than the browser, especially on weak client computers.
 
 4. ??? warning "Optional for *non-TigerVNC* and NOT RECOMMENDED: Enable VNCAuth method"
 
-        This step is nessessory if you're using TightVNC (don't confuse it with TigerVNC!)
-        and some other clients that does not support the user/password auth method.
+        This step is nessessory if you're using a client that does not support the user/password
+        auth method like TightVNC (don't confuse it with TigerVNC).
 
-        In this case you can enable single VNCAuth passphrases mode in `/etc/kvmd/override.yaml`:
+        In this case you can enable VNCAuth passphrases mode in `/etc/kvmd/override.yaml`:
 
         ```yaml
         vnc:
@@ -59,7 +60,7 @@ than the browser, especially on weak client computers.
 
         To set passphrases edit the file `/etc/kvmd/vncpasswd`.
 
-        But once again: **this is an unsafe authorization method** and it is better to use TigerVNC.
+        **But once again: THIS IS AN UNSAFE AUTHORIZATION METHOD and it is better to use TigerVNC.**
 
 5. Enable `kvmd-vnc` daemon. VNC will be available on the port 5900: `systemctl enable --now kvmd-vnc`.