Fix prettier format

docs/config/inbound.md

@@ -114,7 +114,6 @@
 
 当流量为指定类型时，按其中包括的目标地址重置当前连接的目标。
 
-
 ::: tip
 Xray只会嗅探 `destOverride` 中协议的域名用作路由，如果只想进行嗅探用作路由而不想重置目标地址（如使用Tor浏览器时，重置目标地址会导致无法连接），请在这里添加对应的协议并启用 `routeOnly` 。
 :::

docs/config/transport.md

@@ -823,7 +823,6 @@ PS: 如果有正常上网的域名流量被 AsIs 的 freedom 出站送过来，
 
 当 type 指定为 int 时需要使用十进制数字。
 
-
 > `happyEyeballs`: {}
 
 RFC-8305 实现的 happyEyeballs 仅适用于 TCP, 当目标为域名时对它们竞速并选择第一个成功的返回，当 `domainStrategy` 被设置为 `UseIP`/`ForceIP` (包括它们的v4/v6/v4v6版本，但这会使可用的IP列表被缩减到仅剩v4或v6，不推荐这么用)

docs/en/config/inbound.md

@@ -109,7 +109,6 @@ Whether to enable traffic sniffing.
 
 When the traffic is of a specified type, reset the destination of the current connection to the target address included in the list.
 
-
 > `metadataOnly`: true | false
 
 When enabled, only use the connection's metadata to sniff the target address. In this case, sniffer other than `fakedns` cannot be activated.

docs/en/config/outbounds/freedom.md

@@ -36,8 +36,8 @@ Freedom is an outbound protocol that can be used to send (normal) TCP or UDP dat
 ```
 
 > `domainStrategy`: "AsIs"
-"UseIP" | "UseIPv6v4" | "UseIPv6" | "UseIPv4v6" | "UseIPv4"
+> "UseIP" | "UseIPv6v4" | "UseIPv6" | "UseIPv4v6" | "UseIPv4"
-"ForceIP" | "ForceIPv6v4" | "ForceIPv6" | "ForceIPv4v6" | "ForceIPv4"
+> "ForceIP" | "ForceIPv6v4" | "ForceIPv6" | "ForceIPv4v6" | "ForceIPv4"
 
 When the destination address is a domain name, configure the corresponding value for Freedom's behavior:
 

docs/en/config/transport.md

@@ -520,8 +520,8 @@ When `followRedirect` is set to `true` in [Dokodemo-door](./inbounds/dokodemo.md
 :::
 
 > `domainStrategy`: "AsIs"
-"UseIP" | "UseIPv6v4" | "UseIPv6" | "UseIPv4v6" | "UseIPv4"
+> "UseIP" | "UseIPv6v4" | "UseIPv6" | "UseIPv4v6" | "UseIPv4"
-"ForceIP" | "ForceIPv6v4" | "ForceIPv6" | "ForceIPv4v6" | "ForceIPv4"
+> "ForceIP" | "ForceIPv6v4" | "ForceIPv6" | "ForceIPv4v6" | "ForceIPv4"
 
 In previous versions, when Xray attempted to establish a system connection using a domain name, the resolution of the domain name was completed by the system and not controlled by Xray. This led to issues such as the inability to resolve domain names in non-standard Linux environments. To solve this problem, Xray 1.3.1 introduced Freedom's `domainStrategy` into Sockopt.
 
@@ -659,7 +659,6 @@ The option value to be set, the example here is set to bbr.
 
 Decimal numbers are required when type is specified as int.
 
-
 > `happyEyeballs`: {}
 
 only TCP, this is RFC-8305 implementation of happyEyeballs, only apply when built-in-dns is used(domainStrategy is `UseIP`/`ForceIP`).

docs/en/document/install.md

@@ -90,6 +90,7 @@ Currently two different styles of Docker images are provided:
 ### Docker Image File Structure
 
 teddysun/xray image:
+
 - `/usr/bin/xray`: Xray-core executable
 - `/etc/xray/config.json`: Single configuration file (its directory is the mount point)
 - `/usr/share/xray/`: Resource directory containing v2fly geodata files
@@ -97,6 +98,7 @@ teddysun/xray image:
   - geosite.dat
 
 ghcr.io/xtls/xray-core image:
+
 - `/usr/local/bin/xray`: Xray-core executable (owner: root:root, permissions: 755)
 - `/usr/local/etc/xray/`: Configuration directory (mount point). Owner: root:root, directory permissions: 755, file permissions: 644
   - 00_log.json

docs/ru/config/inbound.md

@@ -125,7 +125,6 @@
 
 Заменить целевой адрес текущего подключения на указанные типы, если трафик соответствует им.
 
-
 ::: tip
 Xray будет использовать доменные имена, обнаруженные с помощью sniffing, только для маршрутизации.  
 Если вы хотите только обнаруживать доменные имена для маршрутизации, но не хотите изменять целевой адрес (например, при использовании Tor Browser изменение целевого адреса может привести к невозможности подключения), добавьте соответствующие протоколы в этот список и включите `routeOnly`.