fix

docs/use/hosts.md

@@ -6,11 +6,11 @@ import DocCard from '@theme/DocCard';
 
 Think of a Host as the gateway that directs users to your Nodes.
 
-When users get a **subscription URL** and add it to their client app, the app fetches a list of available Hosts. Each Host contains the connection details like server address and port, guiding the user to the right Node.
+When users get a subscription URL and add it to their client app, the app fetches a list of available Hosts. Each Host contains the connection details like server address and port, guiding the user to the right Node.
 
 Here’s how it works:
 
-1. The user receives a subscription URL.
+1. The user receives a subscription URL and imports it into the client app.
 2. The client app retrieves a list of available Hosts.
 3. The user picks a Host, which connects them to the associated Node.
 

docs/use/quick-start.md

@@ -28,8 +28,6 @@ If you ever forget your password, you can always recreate the super-admin accoun
 To access the Rescue CLI, use the command: `docker exec -it remnawave remnawave-rescue-cli`
 :::
 
----
-
 ## Home Page {#home}
 
 After registration, you will be taken to the main dashboard.
@@ -79,6 +77,7 @@ On the left side you will see the navigation menu:
     * `Users` -  Create and manage [Users](/docs/use/users).
     * `Internal Squads` - Configure [Internal Squads](/docs/use/internal-squads).
     * `Config Profiles` - Create and manage [Xray-core configurations](/docs/use/config-profiles).
+    * `Hosts` - Manage [entry points](/docs/use/hosts) for users.
     * `Nodes`:
         - `Management` - View, edit, disable, or delete [Nodes](/docs/use/nodes).
         - `Statistics` - Review detailed usage statistics per Node.

docs/use/templates.md

@@ -8,7 +8,7 @@ As mentioned earlier, when you create a user, they’re assigned a Subscription
 
 You probably noticed that when we opened our subscription URL in a browser, we saw a human-readable webpage. But when we added the same URL to a client app, it imported without any issues.
 
-This happens because Remnawave automatically detects which client application is making the subscription request:
+This happens because Remnawave automatically detects who is accessing the URL:
 
 When opened from a browser, Remnawave recognizes it and serves the webpage.