From 5c48d1c544ae1129b718bc9fd0ddd55aa007b374 Mon Sep 17 00:00:00 2001
From: RustDesk <71636191+rustdesk@users.noreply.github.com>
Date: Wed, 27 Nov 2024 17:32:17 +0800
Subject: [PATCH] Updated FAQ (markdown)

---
 FAQ.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/FAQ.md b/FAQ.md
index 29cc5bc..1ad414a 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -534,7 +534,7 @@ Here is how TeamViewer defines concurrent connections: it is the number of indiv
 
 For example, on one machine A, you can connect to B, C, D, etc., at the same time without limitation. Each outgoing connection in this case is a session, and all of these sessions together are called one channel; unlimited concurrent outgoing sessions are allowed on one machine or in one channel. However, you cannot establish a new connection from B to C while there is an outgoing connection on A at the same time if your license allows only one concurrent connection.
 
-For Example you have support Agent A who is talking to Customer C and Now Agent B wants to communicate with Customer D when Agent A is Connected to Customer C, Then How many concurrent connection do we need? You need 2.
+For Example we have support Agent A who is talking to Customer C and Now Agent B wants to communicate with Customer D when Agent A is Connected to Customer C, Then How many concurrent connection do we need? You need 2.
 
 https://community.teamviewer.com/English/discussion/10470/the-maximum-number-of-your-concurrent-teamviewer-sessions-has-been-reached