From 8982c9fa7fff5a0a25e502391833f5b3b693b1d0 Mon Sep 17 00:00:00 2001
From: Kasm <44181855+kasmtech@users.noreply.github.com>
Date: Wed, 31 Mar 2021 15:40:24 -0400
Subject: [PATCH] Updated Differences From TigerVNC (markdown)

---
 Differences-From-TigerVNC.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Differences-From-TigerVNC.md b/Differences-From-TigerVNC.md
index b274bb4..628ae0d 100644
--- a/Differences-From-TigerVNC.md
+++ b/Differences-From-TigerVNC.md
@@ -1,7 +1,7 @@
 Kasm is focused on being a web native remote desktop server and client. We did not want to be tied down to conforming to the VNC protocol and wanted a single unified application rather than 3 separate components (TigerVNC, noVNC, websockify).
 
 # VNC Protocol
-KasmVNC gets rid of the VNC service which by default listens on port 5901. While you can configure KasmVNC to enable that service, we provides no guarantees that we will keep VNC protocol compatibility. We also do not guarantee that we will upstream changes from TigerVNC that are not applicable to our goals. 
+KasmVNC gets rid of the VNC service which by default listens on port 5901. While you can configure KasmVNC to enable that service, we provide no guarantees that we will keep VNC protocol compatibility. We also do not guarantee that we will upstream changes from TigerVNC that are not applicable to our goals. 
 
 # Authentication
 TigerVNC uses the VNC protocol's password based authentication, which has a limit of 8 characters. We have completely removed the VNC password and replaced it with HTTP Basic Authentication. Eventually we will replace basic auth with a more comprehensive authentication and session handling approach.