Skip to content

chore: fix some minor issues in comments #662

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: fix some minor issues in comments #662

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion run-on-lido/csm/alerts-and-monitoring/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Whether you’re using built-in dashboards or external services, here’s how to

## Explore the sub-sections

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

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

Expand Down
2 changes: 1 addition & 1 deletion run-on-lido/csm/lido-csm-widget/exiting-csm-validators/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ There are 2 reasons why CSM operators can receive exit request from the Lido Pro
2. If you have unbonded validators you're required to either top up the bond, or exit the validator.

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

You can read more about exits [here](/staking-modules/csm/validator-exits).
Expand Down
2 changes: 1 addition & 1 deletion run-on-lido/csm/lido-csm-widget/operator-roles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ It's optimal to set the Manager to a *hot* address and the Rewards to a secure *
### Optimal for DVT clusters
There's multiple ways to set up a DVT cluster using CSM.

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.
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.

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

Expand Down