From 39ea5475655c2118f0638b422a3d637d131ce21a Mon Sep 17 00:00:00 2001
From: RustDesk <71636191+rustdesk@users.noreply.github.com>
Date: Sun, 1 Jun 2025 16:23:31 +0800
Subject: [PATCH] Updated FAQ (markdown)

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

diff --git a/FAQ.md b/FAQ.md
index 90362b2..e3414b5 100644
--- a/FAQ.md
+++ b/FAQ.md
@@ -72,16 +72,15 @@ The hardware requirements are very low, the minimum configuration of the cloud s
 
 # Deploy RustDesk server in intranet.
 
-First you should set relay server with public ip explicitly on "settings" -> "relay" of web console. Or you can set relay server (public ip) explcitly on controlled side (remote side, the device you want to control). 
+First you should set relay server with public ip explicitly on "settings" -> "relay" of web console. Or you can set relay server (public ip) explcitly on controlled side (remote side, the device you want to control).
 
 ![image](https://github.com/user-attachments/assets/1831bd14-f7db-4065-ac9f-9ba5f18ab8ef)
 
-
 Go to [access logs](https://github.com/rustdesk/rustdesk/wiki/FAQ#access-logs) on controlled side, you can see more details about failures, also check connection logs `%AppData%\RustDesk\log\RustDesk_rCURRENT.log` on controlling side.
 
 If you host the server in your intranet with some type of routers, you may have network problem because of NAT hairping.
 
-One simple solution for NAT hairping (loopback) is that both internal and external use domain. Internally, use an internal DNS Server to point the domain to an intranet IP.
+One simple solution for NAT hairping (loopback) is that both internal and external use domain. Internally, use an internal DNS Server (or modify your hosts file) to point the domain to an intranet IP.
 
 https://rustdesk.com/docs/en/self-host/nat-loopback-issues/