From fd34ddc4133802dce65f07f16348d26852a336d4 Mon Sep 17 00:00:00 2001
From: RustDesk <71636191+rustdesk@users.noreply.github.com>
Date: Fri, 6 Jun 2025 19:59:59 +0800
Subject: [PATCH] Updated FAQ (markdown)

---
 FAQ.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/FAQ.md b/FAQ.md
index 0becb08..aa0bd69 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -379,9 +379,9 @@ https://github.com/rustdesk/rustdesk/discussions/6398#discussioncomment-9065991
   It may be caused by using wrong volumns mapping in docker compose file, please strictly follow https://rustdesk.com/docs/en/self-host/rustdesk-server-pro/installscript/docker/#docker-compose, or you changed `hbbs` key but forgot to sync to `hbbr` (and restart), or some other reasons.
  > We have seen two cases having this `hbbr` key issue while upgading RustDesk server.
 
-- If your cloud has problem with `21117` connection.
+- If your cloud instance has problem with `21117` connection.
 
-An user reported this, the `hbbr` logs below show the relay succeeded but close (It is FIN close, not RST) quickly. This indicated the connection closure likely occurred mid-stream between the server and client, leading us to suspect a cloud provider issue. The problem was indeed resolved after the user migrated to a different cloud service.
+An user reported this, the `hbbr` logs below show the relay succeeded but close (It is FIN close, not RST) quickly. This indicated the connection closure likely occurred mid-stream between the server and client, leading us to suspect a cloud provider issue. The problem was indeed resolved after the user migrated to a new cloud instance.
 
 ```
 [2025-06-06 05:59:42.978845 +00:00] INFO [src/relay_server.rs:475] New relay request 6b07fbd4-4f29-4721-807b-7c8bd1f6fb02 from [::ffff:114.5.43.33:49925