From bb77432299101dfeacdf31d3946061efe0d132cf Mon Sep 17 00:00:00 2001
From: RustDesk <71636191+rustdesk@users.noreply.github.com>
Date: Fri, 14 Nov 2025 18:03:33 +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 86ef091..ccad364 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -938,7 +938,7 @@ A single technician is always counted as one Login User, regardless of how many
 ## Concurrent connections
 It's the same as the so called channels with teamviewer. 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 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, on one machine A, you can connect to machine 1, 2, 3, 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 new connections from B to machine 1, 2, 3 while there is an outgoing connection on A at the same time if your license allows only one concurrent connection.
 
 A connects to machine 1, 2, 3 at the same time, it is one channel, one current connection is ok.