cerc-io/lighthouse
16
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

Fix two minor typos (#688)

Browse Source
This commit is contained in:
pscott 2019-12-10 02:40:10 +01:00 committed by Paul Hauner
parent 10a134792b
commit e4c56e6c5c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
book/src/become-a-validator.md
View File

@ -38,7 +38,7 @@ Start your beacon node with:
$ lighthouse beacon --eth1 --http $ lighthouse beacon --eth1 --http
``` ```
You're beacon node has started syncing when you see the following (truncated) Your beacon node has started syncing when you see the following (truncated)
log: log:
``` ```
@ -108,7 +108,7 @@ Dec 09 13:09:09.000 INFO Awaiting activation slot: 17787, ..
If your beacon node hasn't finished syncing yet, you'll see some `ERRO` If your beacon node hasn't finished syncing yet, you'll see some `ERRO`
messages indicating that your node isn't synced yet. It is safest to wait for messages indicating that your node isn't synced yet. It is safest to wait for
your node to sync before moving onto the next step, otherwise your validator your node to sync before moving onto the next step, otherwise your validator
may active before you're able to produce blocks and attestations. However, it may activate before you're able to produce blocks and attestations. However, it
generally takes 4-8+ hours after deposit for a validator to become active. If generally takes 4-8+ hours after deposit for a validator to become active. If
your `est_time` is less than 4 hours, you _should_ be fine to just move to the your `est_time` is less than 4 hours, you _should_ be fine to just move to the
next step. After all, this is a testnet and you're only risking Goerli ETH. next step. After all, this is a testnet and you're only risking Goerli ETH.