waku-org
/
nwaku
mirror of https://github.com/waku-org/nwaku.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs: fix typo (#2348)

This commit is contained in:
vuittont60 2024-01-11 22:38:56 +08:00 committed by GitHub
parent 8ce8ec6942
commit a4a8dee34c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
5 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/api/node.md
View File

@ -2,7 +2,7 @@
## Nim API ## Nim API
The Nim Waku API consist of a set of methods opearting on the Waku Node object. The Nim Waku API consist of a set of methods operating on the Waku Node object.
Some of them have different arity depending on what privacy/bandwidth trade-off Some of them have different arity depending on what privacy/bandwidth trade-off
the consumer wants to make. These methods are: the consumer wants to make. These methods are:

2
docs/operators/how-to/configure-domain.md
View File

@ -10,7 +10,7 @@ It is possible to configure an IPv4 DNS domain name that resolves to the node's
wakunode2 --dns4-domain-name=mynode.example.com wakunode2 --dns4-domain-name=mynode.example.com
``` ```
This allows for the node's publically announced `multiaddrs` to use the `/dns4` scheme. This allows for the node's publicly announced `multiaddrs` to use the `/dns4` scheme.
In addition, nodes with domain name and [secure websocket configured](./configure-websocket.md), In addition, nodes with domain name and [secure websocket configured](./configure-websocket.md),
will generate a discoverable ENR containing the `/wss` multiaddr with `/dns4` domain name. will generate a discoverable ENR containing the `/wss` multiaddr with `/dns4` domain name.
This is necessary to verify domain certificates when connecting to this node over secure websocket. This is necessary to verify domain certificates when connecting to this node over secure websocket.

2
docs/operators/how-to/connect.md
View File

@ -1,6 +1,6 @@
# Connect to other peers # Connect to other peers
*Note that this tutorial describes how to **configure** a node to connect to other peers before runnning the node. *Note that this tutorial describes how to **configure** a node to connect to other peers before running the node.
For connecting a running node to existing peers, For connecting a running node to existing peers,
see the [JSON-RPC API](https://rfc.vac.dev/spec/16/).* see the [JSON-RPC API](https://rfc.vac.dev/spec/16/).*

2
docs/operators/how-to/run.md
View File

@ -36,7 +36,7 @@ Different ways to connect to other nodes are expanded upon in our [connection gu
Find the log entry beginning with `Listening on`. Find the log entry beginning with `Listening on`.
It should be printed at INFO level when you start your node It should be printed at INFO level when you start your node
and contains a list of all publically announced listening addresses for the nwaku node. and contains a list of all publicly announced listening addresses for the nwaku node.
For example For example

2
docs/tutorial/dingpu.md
View File

@ -21,7 +21,7 @@ Then type messages to publish.
## Interactively add a node ## Interactively add a node
There is also an interactive mode. Type `/connect` then paste address of other node. However, this currently has some timing issues with mesh not being updated, so it is adviced not to use this until this has been addressed. See https://github.com/waku-org/nwaku/issues/231 There is also an interactive mode. Type `/connect` then paste address of other node. However, this currently has some timing issues with mesh not being updated, so it is advised not to use this until this has been addressed. See https://github.com/waku-org/nwaku/issues/231
## Dingpu cluster node ## Dingpu cluster node