From 532db87ae033fb5041a9b3f1d540feea87e427c7 Mon Sep 17 00:00:00 2001 From: yinwenyu6 Date: Sun, 17 Aug 2025 16:28:44 +0800 Subject: [PATCH] chore: fix some minor issues in comments Signed-off-by: yinwenyu6 --- run-on-lido/csm/alerts-and-monitoring/index.md | 2 +- run-on-lido/csm/lido-csm-widget/exiting-csm-validators/index.md | 2 +- run-on-lido/csm/lido-csm-widget/operator-roles.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/run-on-lido/csm/alerts-and-monitoring/index.md b/run-on-lido/csm/alerts-and-monitoring/index.md index 1e58865f6..7d21c73b0 100644 --- a/run-on-lido/csm/alerts-and-monitoring/index.md +++ b/run-on-lido/csm/alerts-and-monitoring/index.md @@ -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) diff --git a/run-on-lido/csm/lido-csm-widget/exiting-csm-validators/index.md b/run-on-lido/csm/lido-csm-widget/exiting-csm-validators/index.md index 8db304c92..0587b8de3 100644 --- a/run-on-lido/csm/lido-csm-widget/exiting-csm-validators/index.md +++ b/run-on-lido/csm/lido-csm-widget/exiting-csm-validators/index.md @@ -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). diff --git a/run-on-lido/csm/lido-csm-widget/operator-roles.md b/run-on-lido/csm/lido-csm-widget/operator-roles.md index 49f1b33f3..70f67349d 100644 --- a/run-on-lido/csm/lido-csm-widget/operator-roles.md +++ b/run-on-lido/csm/lido-csm-widget/operator-roles.md @@ -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)