Skip to content

Commit 532db87

Browse files
committed
chore: fix some minor issues in comments
Signed-off-by: yinwenyu6 <yinwenyu6@outlook.com>
1 parent 017929e commit 532db87

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

run-on-lido/csm/alerts-and-monitoring/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ Whether you’re using built-in dashboards or external services, here’s how to
1010

1111
## Explore the sub-sections
1212

13-
[**Begginer: CSM Widget, EthSeer, Beaconcha.in →**](./beginner-csm-widget-ethseer-beaconcha.in)
13+
[**Beginner: CSM Widget, EthSeer, Beaconcha.in →**](./beginner-csm-widget-ethseer-beaconcha.in)
1414

1515
[**Intermediate: Other External Dashboards →**](./intermediate-other-external-dashboards)
1616

run-on-lido/csm/lido-csm-widget/exiting-csm-validators/index.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ There are 2 reasons why CSM operators can receive exit request from the Lido Pro
1515
2. If you have unbonded validators you're required to either top up the bond, or exit the validator.
1616

1717
If the operator does not exit their validators after the protocol request, the following will be applied:
18-
1. Exclude the Node Operator from the CSM deposit queue until the issue is resovled.
18+
1. Exclude the Node Operator from the CSM deposit queue until the issue is resolved.
1919
2. Exclude the Node Operator from the staking rewards allocation cycle.
2020

2121
You can read more about exits [here](/staking-modules/csm/validator-exits).

run-on-lido/csm/lido-csm-widget/operator-roles.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,7 @@ It's optimal to set the Manager to a *hot* address and the Rewards to a secure *
8888
### Optimal for DVT clusters
8989
There's multiple ways to set up a DVT cluster using CSM.
9090

91-
1. Set the Manager address to a *hot* wallet controled by the cluster coordinator and the Rewards to a cluster mulgisig. This option is only recommended in cases where cluster participants trust the coordinator completely (or have other types of guarantees/agreements in place) or if the DVT setup is an intra-operator setup rather than an inter-operator setup.
91+
1. Set the Manager address to a *hot* wallet controlled by the cluster coordinator and the Rewards to a cluster mulgisig. This option is only recommended in cases where cluster participants trust the coordinator completely (or have other types of guarantees/agreements in place) or if the DVT setup is an intra-operator setup rather than an inter-operator setup.
9292

9393
![roles-7](/img/csm-guide/roles-7.png)
9494

0 commit comments

Comments
 (0)