diff --git a/documentation/docs/src/clients/socks5-client.md b/documentation/docs/src/clients/socks5-client.md index a171cc28d7..39c621dd3b 100644 --- a/documentation/docs/src/clients/socks5-client.md +++ b/documentation/docs/src/clients/socks5-client.md @@ -69,7 +69,7 @@ You can check that your binaries are properly compiled with: ~~~admonish example collapsible=true title="Console output" ``` -# + ``` ~~~ @@ -88,7 +88,7 @@ Before you can use the client, you need to initalise a new instance of it, which ~~~admonish example collapsible=true title="Console output" ``` -# + ``` ~~~ @@ -118,13 +118,6 @@ You can run the initalised client by doing this: ./nym-socks5-client run --id docs-example ``` -~~~admonish example collapsible=true title="Console output" - -``` -# -``` -~~~ - ## Using your Socks5 Client After completing the steps above, your local Socks5 Client will be listening on `localhost:1080` ready to proxy traffic to the Network Requester set as the `--provider` when initialising. diff --git a/documentation/docs/src/clients/websocket-client.md b/documentation/docs/src/clients/websocket-client.md index 004724befc..65b1f4ab86 100644 --- a/documentation/docs/src/clients/websocket-client.md +++ b/documentation/docs/src/clients/websocket-client.md @@ -190,11 +190,11 @@ In some applications, e.g. where people are chatting with friends who they know, } ``` -If that fits your security model, good. However, it may be the case that you want to send **anonymous replies using Single Use Reply Blocks (SURBs)**. +If that fits your security model, good. However, will probably be the case that you want to send **anonymous replies using Single Use Reply Blocks (SURBs)**. You can read more about SURBs [here](../architecture/traffic-flow.md#private-replies-using-surbs) but in short they are ways for the receiver of this message to anonymously reply to you - the sender - without them having to know your nym address. -Your client will send along a number of `replySurbs` to the recipient of the message. These are pre-addressed Sphinx packets that the recipient can write to, but not view the address. If the recipient is unable to fit the response data into the bucket of SURBs sent to it, it will use a SURB to request more SURBs be sent to it. +Your client will send along a number of `replySurbs` to the recipient of the message. These are pre-addressed Sphinx packets that the recipient can write to the payload of (i.e. write response data to), but not view the address. If the recipient is unable to fit the response data into the bucket of SURBs sent to it, it will use a SURB to request more SURBs be sent to it from your client. ```json { diff --git a/documentation/docs/src/nodes/network-requester-setup.md b/documentation/docs/src/nodes/network-requester-setup.md index 1ff1a85e8f..91011ff909 100644 --- a/documentation/docs/src/nodes/network-requester-setup.md +++ b/documentation/docs/src/nodes/network-requester-setup.md @@ -97,21 +97,6 @@ When running the above commands, the `./nym-network-requester --help ` command c ``` ~~~ -## Running your network requester - -Once an network-requester has been initialized, we can start it with the following command: - -``` - ./nym-network-requester run --id example -``` - -Expected output: - -~~~admonish example collapsible=true title="Console output" -``` - - ``` -~~~ ## Upgrading your network requester You can upgrade your network requester by following these steps: @@ -120,7 +105,7 @@ You can upgrade your network requester by following these steps: * replace the old binary with the new binary * restart your service using the commands in the previous section of the document -### Upgrading to version 1.1.10 +### Upgrading to >= v1.1.10 from