Skip to content

Commit eab8969

Browse files
committed
Fix Lido CSM Steps
1 parent 92d888a commit eab8969

File tree

1 file changed

+3
-3
lines changed
  • docs/03-installation/02-use-case-guides/03-node-operator/lido

1 file changed

+3
-3
lines changed

docs/03-installation/02-use-case-guides/03-node-operator/lido/03-lido-csm.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,12 +24,12 @@ Ensure you set the appropriate data path for your server by selecting the right
2424
### Step 5
2525
The next step involves setting the synchronization method for your node clients. The recommended 'Checkpoint Sync' method allows a quicker synchronization with the blockchain by starting from a known good state. Choose a trusted source for your checkpoint, which will influence the integrity and reliability of your node's data.
2626

27-
![Step 5 Screenshot](../../../../../static/screenshots/guides/lido-csm-operator/lido-csm-5.png)
27+
![Step 6 Screenshot](../../../../../static/screenshots/guides/lido-csm-operator/lido-csm-6.png)
2828

2929
### Step 6
30-
Choose from a range of block relays available for your node. Each relay offers different performance characteristics and geographical distribution. Select the block relays that best fit your operational requirements and expected validator performance.
30+
Keep the relay selection as is, as these are the necessary relays mandated to run Lido CSM.
3131

32-
![Step 6 Screenshot](../../../../../static/screenshots/guides/lido-csm-operator/lido-csm-6.png)
32+
![Step 5 Screenshot](../../../../../static/screenshots/guides/lido-csm-operator/lido-csm-5.png)
3333

3434
### Step 7
3535
Finally, you’ll confirm the installation paths for each component you’re setting up on your server. This summary screen lists all the chosen services with their respective categories and installation paths, ensuring you have a clear overview of where each service will reside on the server. It’s important to verify that each path is correct to prevent any future operational issues.

0 commit comments

Comments
 (0)