gnosis/lighthouse
1
0
Fork 0
mirror of https://github.com/sigp/lighthouse.git synced 2026-03-23 23:04:53 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix typos (#5059)

Browse Source 
* docs: fix typos

* docs: fix typo

* docs: update by 'make cli'
This commit is contained in:
vuittont60
2024-01-16 09:18:54 +08:00
committed by GitHub
parent 31b797ed83
commit 0613eb7a21
8 changed files with 8 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
book/src/help_bn.md
View File

@@ -29,7 +29,7 @@ FLAGS:
contention which degrades staking performance. Stakers should generally
choose to avoid this flag since backfill sync is not required for
staking.
--disable-deposit-contract-sync Explictly disables syncing of deposit logs from the execution node. This
--disable-deposit-contract-sync Explicitly disables syncing of deposit logs from the execution node. This
overrides any previous option that depends on it. Useful if you intend to
run a non-validating beacon node.
--disable-duplicate-warn-logs Disable warning logs for duplicate gossip messages. The WARN level log is

2
book/src/redundancy.md
View File

@@ -97,7 +97,7 @@ from this list:
setup this is the first option we would recommend enabling.
- `sync-committee`: Send sync committee signatures & aggregates to all beacon nodes. This can
improve propagation of sync committee messages with similar tradeoffs to broadcasting
attestations, although occuring less often due to the infrequency of sync committee duties.
attestations, although occurring less often due to the infrequency of sync committee duties.
- `none`: Disable all broadcasting. This option only has an effect when provided alone, otherwise
it is ignored. Not recommended except for expert tweakers.

2
book/src/slasher.md
View File

@@ -71,7 +71,7 @@ If an MDBX database is already found on disk, then Lighthouse will try to use it
in a log at start-up:
```
INFO Slasher backend overriden reason: database exists, configured_backend: lmdb, overriden_backend: mdbx
INFO Slasher backend overridden reason: database exists, configured_backend: lmdb, overridden_backend: mdbx
```
If the running Lighthouse binary doesn't have the MDBX backend enabled but an existing database is

2
book/src/validator-manager-create.md
View File

@@ -139,7 +139,7 @@ In order to import the validators, the location of the VC `api-token.txt` file
must be known. The location of the file varies, but it is located in the
"validator directory" of your data directory. For example:
`~/.lighthouse/mainnet/validators/api-token.txt`. We will use `<API-TOKEN-PATH>`
to subsitute this value. If you are unsure of the `api-token.txt` path, you can run `curl http://localhost:5062/lighthouse/auth` which will show the path.
to substitute this value. If you are unsure of the `api-token.txt` path, you can run `curl http://localhost:5062/lighthouse/auth` which will show the path.
Once the VC is running, use the `import` command to import the validators to the VC: