Remove legacy timeout config (#577)

* Remove `timeout` field in dokodemo-door

* Remove `timeout` field in HTTP inbound

* Minor fixes to The Great Chronicles

* Force update wireguard inbound to russian docs

docs/en/about/news.md

@@ -107,16 +107,16 @@ Added HTTPUpgrade transport, said to be lighter than WebSocket.
 
 gRPC transport now also has a Host-like configuration field! It's called `authority`. Now gRPC can also "domain front," without ALPN issues.
 
-## 2024.1.9
-
-Shocked to hear that Win7 cannot run the new version of Xray-core? Upon exploration, it was discovered that Go has dropped support for Win7. Is there a way to continue supporting this somewhat ancient but still elegant operating system?
-
 ## 2024.2.25 <Badge>[v1.8.8](https://github.com/XTLS/Xray-core/releases/tag/v1.8.8)</Badge>
 
 - Now XUDP traffic is uniformly padded with Vision, come and experience it.
 - Added leastLoad balancer.
 - Fixed errors, optimized performance...
 
+## 2024.1.9
+
+Shocked to hear that Win7 cannot run the new version of Xray-core? Upon exploration, it was discovered that Go has dropped support for Win7. Is there a way to continue supporting this somewhat ancient but still elegant operating system?
+
 ## 2023.11.21
 
 The [paper](https://t.me/projectXtls/212) published at the USENIX top conference confirms that XTLS Vision has achieved its design goals. And XTLS will not stop there, breaking through towering walls like X-rays.
@@ -174,8 +174,7 @@ Maybe we can leverage [RealiTLScanner](https://github.com/XTLS/RealiTLScanner)
 
 ## 2023.4.20
 
-After years of development and countless lines of code...
-The code simplification plan has been proposed!
+After years of development and countless lines of code... [The code simplification plan](https://github.com/XTLS/Xray-core/discussions/1967) has been proposed!
 
 ## 2023.4.19
 
@@ -216,6 +215,7 @@ XTLS Vision has also been improved, please upgrade both ends to the latest versi
 ## 2023.3.4
 
 > Legends never die, they become a part of ~~you~~ VLESS.
+>
 > They simply fade away.
 
 ## 2023.3.2
@@ -390,7 +390,7 @@ Brought an improvement to tun2socks. You might get to enjoy it in the future~
 
 ## 2021.4.12
 
-Introducing X-flutter preview; looking forward to what it might be like~ ~~🍪~~
+Let's foresee X-flutter; looking forward to what it might be like~ ~~🍪~~
 
 ## 2021.4.6
 

docs/en/config/inbounds/dokodemo.md

@@ -9,7 +9,6 @@ Dokodemo door (Anywhere Door) can listen to a local port and forward all incomin
   "address": "8.8.8.8",
   "port": 53,
   "network": "tcp",
-  "timeout": 0,
   "followRedirect": false,
   "userLevel": 0
 }
@@ -29,10 +28,6 @@ The specified port on the destination address to forward the traffic to. It shou
 
 The supported network protocol type. For example, when specified as `"tcp"`, it will only receive TCP traffic. The default value is `"tcp"`.
 
-> `timeout`: number
-
-The idle timeout in seconds. The default value is `300`. When handling a connection, if no data is transmitted within the timeout period, the connection will be terminated.
-
 > `followRedirect`: true | false
 
 When set to `true`, dokodemo-door will recognize data forwarded by iptables and forward it to the corresponding destination address.
@@ -45,6 +40,32 @@ The user level that the connection will use to determine the corresponding [Loca
 
 The value of `userLevel` corresponds to the value of `level` in the [policy](../policy.md#policyobject). If not specified, the default value is 0.
 
+## Usage
+
+Dokodemo-door can be used as Transparent proxy (in the next section) and can be used to mapping a port.
+
+Some services does not support proxy likes SOCKS5, but using Tun or Tproxy could be too complicated. If these services only communicate with only one port (like iperf, Minecraft server, Wireguard endpoint, etc.), dokodemo-door can be used.
+
+Below is an example config (if the default outbound is an effective proxy):
+
+```json
+{
+  "listen": "127.0.0.1",
+  "port": 25565,
+  "protocol": "dokodemo-door",
+  "settings": {
+    "address": "mc.hypixel.net",
+    "port": 25565,
+    "network": "tcp",
+    "followRedirect": false,
+    "userLevel": 0
+  },
+  "tag": "mc"
+}
+```
+
+The core will listen at `127.0.0.1:25565`, and the traffic coming in through this inbound will be send to `mc.hypixel.net:25565` (a Minecraft server) through the default outbound. Then you can connect the Minecraft client to the Hypixel server through the proxy by set the game server to `127.0.0.1:25565` in the Minecraft client.
+
 ## Transparent Proxy Configuration Example
 
 Please refer to the [Transparent Proxy (TProxy) Configuration Tutorial](../../document/level-2/tproxy) for this section.

docs/en/config/inbounds/http.md

@@ -23,7 +23,6 @@ In Linux, you can use the following environment variables to enable global HTTP
 
 ```json
 {
-  "timeout": 0,
   "accounts": [
     {
       "user": "my-username",
@@ -35,12 +34,6 @@ In Linux, you can use the following environment variables to enable global HTTP
 }
 ```
 
-> `timeout`: number
-
-The idle timeout in seconds. The default value is `300`, and 0 means no timeout.
-
-When handling a connection, if no data is transmitted within the timeout period, the connection will be terminated.
-
 > `accounts`: \[[AccountObject](#accountobject)\]
 
 An array where each element represents a user account. The default value is an empty array.