From 52c8621d26cf2b5886b483736c8a0c80d756005f Mon Sep 17 00:00:00 2001
From: RustDesk <71636191+rustdesk@users.noreply.github.com>
Date: Sat, 26 Oct 2024 09:28:35 +0800
Subject: [PATCH] Updated FAQ (markdown)

---
 FAQ.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/FAQ.md b/FAQ.md
index 4bb3c58..19edd62 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -510,7 +510,9 @@ You need to log in to the RustDesk client first to access address books and perm
 
 ![image](https://github.com/user-attachments/assets/189e6c73-eaef-40e0-bba8-fed3db1f758b)
 
-- Here is how TeamViewer defines concurrent connections: it is the number of individual users who can make outgoing connections simultaneously.
+- Here is how TeamViewer defines concurrent connections: it is the number of individual users who can make outgoing connections simultaneously. You can also call it channel, in the same channel, unlimited sessions are allowed. 
+
+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 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."
 
 https://community.teamviewer.com/English/discussion/10470/the-maximum-number-of-your-concurrent-teamviewer-sessions-has-been-reached