From 2dcfe5dae41fa265edda9ebb28f97916d8496720 Mon Sep 17 00:00:00 2001
From: PentiumB <5298.avgan.5298@gmail.com>
Date: Thu, 24 Jul 2025 12:30:57 +0500
Subject: [PATCH] Update remnawave-node.md

---
 docs/install/remnawave-node.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/install/remnawave-node.md b/docs/install/remnawave-node.md
index c2c4966..f8b076c 100644
--- a/docs/install/remnawave-node.md
+++ b/docs/install/remnawave-node.md
@@ -71,7 +71,7 @@ docker compose up -d && docker compose logs -f -t
 
 :::info
 WARNING!
-1. This manual does not contain mandatory instructions, it is only an example of implementation without reference to the file `zapret.dat` used in it. In your implementation, it will not be appropriate to blindly repeat the call ext:zapret.dat:zapret, since in reality the categories `:zapret` will be different. If you blindly, without understanding what is happening, repeat what is described, you will break your Xray configuration and get an error connecting to the node.
+1. This manual does not contain mandatory instructions, it is only an example of implementation without reference to the file `*-zapret.dat` used in it. In your implementation, it will not be appropriate to blindly repeat the call ext:*-zapret.dat:zapret, since in reality the categories `:zapret` will be different. If you blindly, without understanding what is happening, repeat what is described, you will break your Xray configuration and get an error connecting to the node.
 2. If you imagine that you will configure this routing on your server, and this will mean that client connections will be guided by this routing - you are mistaken.
 For example: If you configure so that the sites of your country go directly from your Internet (Direct). This will not mean that the client application will work this way, the client routing is responsible for this.