Remove all illegal commas

docs/en/config/fakedns.md

@@ -124,7 +124,7 @@ In addition, you need to enable `Sniffing` in the **client** for incoming traffi
   "enabled": true,
   "destOverride": ["fakedns"], // Use "fakedns", or use it with other sniffer.
   "metadataOnly": false        // When this item is true, destOverride can only use fakedns.
-},
+}
 ```
 
 ::: warning

docs/en/config/outbounds/loopback.md

@@ -28,7 +28,7 @@ If you need to do some more detailed routing for traffics that have been routed
       "tag": "need-to-split",
       "settings": {
         "inboundTag": "traffic-input", // This tag will be used as the inboundTag inside the RuleObject
-      },
+      }
     },
     {
       "tag": "tcp-output",
@@ -44,14 +44,14 @@ If you need to do some more detailed routing for traffics that have been routed
       {
         "inboundTag": ["traffic-input"], // tag set in the loopback outbound setting
         "network": "tcp",
-        "outboundTag": "tcp-output",
+        "outboundTag": "tcp-output"
       },
       {
         "inboundTag": ["traffic-input"], // tag set in the loopback outbound
         "network": "udp",
-        "outboundTag": "udp-output",
+        "outboundTag": "udp-output"
       },
-    ],
-  },
+    ]
+  }
 }
 ```

docs/en/config/outbounds/wireguard.md

@@ -98,7 +98,7 @@ When the destination address is a domain name, use the Xray-core [built-in DNS s
             }
         ],
         "queryStrategy": "UseIP" // If this parameter is not written, the default value is UseIP, i.e. both A and AAAA records are queried, optional values are UseIPv4 and UseIPv6, other record types are queried by the system DNS.
-    },
+    }
 ```
 
 **Note 2**：

docs/en/config/transport.md

@@ -675,7 +675,7 @@ in `freedom` settings when you set `domainStrategy` to `UseIP`/`ForceIP` just a
     "tryDelayMs": 250,
     "prioritizeIPv6": false,
     "interleave": 1,
-    "maxConcurrentTry": 4,
+    "maxConcurrentTry": 4
 }
 ```
 

docs/en/config/transports/mkcp.md

@@ -10,7 +10,7 @@ Make sure the firewall on the host is configured correctly.
 
 ## KcpObject
 
-`KcpObject` corresponds to the `kcpSettings` in the [Transport Protocol](../transport.md),
+`KcpObject` corresponds to the `kcpSettings` in the [Transport Protocol](../transport.md)
 
 ```json
 {

docs/en/document/level-2/warp.md

@@ -70,7 +70,7 @@ Add the following to the existing router:
                     "geoip:cn"
                 ],
                 "outboundTag": "wireguard-1"
-            },
+            }
 ```
 
 ## Using Warp Chain Proxy on the Client Side