Skip to content

Commit

Permalink
docs: fix minor formatting typos
Browse files Browse the repository at this point in the history
  • Loading branch information
Azadzadeh committed Dec 17, 2022
1 parent 8bb941e commit d880817
Show file tree
Hide file tree
Showing 3 changed files with 4 additions and 4 deletions.
2 changes: 1 addition & 1 deletion docs/content/en/advance/forward.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ You can use Trojan-Go to set up tunnels. A typical application is to use Trojan-

forward is essentially a client, but you need to fill in the ```target_addr``` and ```target_port``` fields to indicate the target of the reverse proxy.

After using this configuration file, the local 53 TCP and UDP ports will be listened to, and all TCP or UDP data sent to the local 53 port will be forwarded to the remote server your_awesome_server via TLS tunnel, and after the remote server gets a response, the data will be returned to the local 53 port via the tunnel. In other words, you can treat 127.0.0.1 as a DNS server, and the results of the local query and the remote server query are the same. You can use this configuration to bypass DNS pollution.
After using this configuration file, the local 53 TCP and UDP ports will be listened to, and all TCP or UDP data sent to the local 53 port will be forwarded to the remote server ```your_awesome_server``` via TLS tunnel, and after the remote server gets a response, the data will be returned to the local 53 port via the tunnel. In other words, you can treat 127.0.0.1 as a DNS server, and the results of the local query and the remote server query are the same. You can use this configuration to bypass DNS pollution.

On the same principle, you can build a Google mirror locally

Expand Down
4 changes: 2 additions & 2 deletions docs/content/en/basic/full-config.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: "Full profile"
title: "Full configuration file"
draft: false
weight: 30
---
Expand Down Expand Up @@ -278,7 +278,7 @@ Thanks to the use of AEAD, trojan-go can correctly determine if the request is v

### ```transport_plugin``` Transport layer plugin options

```Enabled`` Whether to enable transport layer plug-in instead of TLS transport. Once transport layer plugin support is enabled, trojan-go will transmit **unencrypted TLS-encrypted trojan protocol traffic in plaintext to the plugin** to allow user-defined obfuscation and encryption of the traffic.
```Enabled``` Whether to enable transport layer plug-in instead of TLS transport. Once transport layer plugin support is enabled, trojan-go will transmit **unencrypted TLS-encrypted trojan protocol traffic in plaintext to the plugin** to allow user-defined obfuscation and encryption of the traffic.

```type``` plug-in types. The currently supported types are

Expand Down
2 changes: 1 addition & 1 deletion docs/content/en/developer/api.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ draft: false
weight: 100
---

Trojan-Go implements an API based on gRPC, using protobuf to exchange data. The client can get the traffic and speed information; the server can get the traffic, speed, online situation of each user, and dynamically add and delete users and limit the speed. The API module can be activated by adding the ```api`` option to the configuration file. Here is an example, the meaning of each field can be found in the section "Complete configuration file".
Trojan-Go implements an API based on gRPC, using protobuf to exchange data. The client can get the traffic and speed information; the server can get the traffic, speed, online situation of each user, and dynamically add and delete users and limit the speed. The API module can be activated by adding the ```api``` option to the configuration file. Here is an example, the meaning of each field can be found in the section {{< ref "Full configuration file" >}}.

```json
...
Expand Down

0 comments on commit d880817

Please sign in to comment.