fix: text

Author: Jeday

run-on-lido/stvaults/building-guides/pooled-staking-product/index.md

@@ -211,10 +211,10 @@ Confirming tier change request requires applying fresh report to vault. [Read mo
 
 Use `--wallet-connect` option for all commands or provide private key to CLI `.env`
 
-1. Get addresses of your contracts:
+1. Get addresses of your contracts: `yarn start defi-wrapper use-cases wrapper-operations read info <poolAddress>`
 2. Get address of your timelock contract: `yarn start defi-wrapper use-cases timelock-governance common get-timelock-address <poolAddress>`
 3. Connect wallet that holds the proposer role to CLI
-4. `yarn start defi-wrapper use-cases timelock-governance dashboard write propose-change-tier [timelockAddress] [dashboard] [tierId] [shareLimit]`
+4. `yarn start defi-wrapper use-cases timelock-governance dashboard write propose-change-tier <timelockAddress> <dashboard> <tierId> ,<shareLimit>`
 
 #### Etherscan
 
@@ -242,9 +242,9 @@ Use `--wallet-connect` option for all commands or provide private key to CLI `.e
 
 #### CLI
 
-1. Wait for the timelock delay period to pass. You can verify the operation is ready by calling `yarn start defi-wrapper use-cases timelock-governance common read get-last-operations [timelock]`
+1. Wait for the timelock delay period to pass. You can verify the operation is ready by calling `yarn start defi-wrapper use-cases timelock-governance common read get-last-operations <timelock>`
 1. Connect wallet that holds the executor role to CLI
-1. `yarn start defi-wrapper use-cases timelock-governance dashboard write execute-change-tier [timelock] [dashboard] [tierId] [shareLimit]`
+1. `yarn start defi-wrapper use-cases timelock-governance dashboard write execute-change-tier <timelock> <dashboard> <tierId> <shareLimit>`
 
 #### Etherscan
 
@@ -270,7 +270,7 @@ Within the confirmation time window period (default 24 hours) after step 2, the
 
 #### stVaults UI
 
-1. Go to `https://stvaults.lido.fi/vaults/[vaultAdress]/settings/tier`
+1. Go to `https://stvaults.lido.fi/vaults/[vaultAddress]/settings/tier`
 2. Connect wallet that has Node operator address
 3. Follow UI to confirm tier change
 

run-on-lido/stvaults/building-guides/pooled-staking-product/roles-and-permissions.md

@@ -15,7 +15,7 @@ DeFi Wrapper is deployed as a set of on-chain contracts (Pool, Withdrawal Queue,
 ## TimelockController roles (governance)
 
 :::info
-Use CLI `yarn start defi-wrapper use-cases timelock-governance --help` to get list of commands to operate TimelockController. There are shortcut commands for governing roles and other common operations for the DeFi wrapper.  
+Use CLI `yarn start defi-wrapper use-cases timelock-governance --help` to get list of commands to operate TimelockController. There are shortcut commands for governing roles and other common operations for the DeFi wrapper.
 :::
 
 `TimelockController` is deployed together with the pool and becomes the admin for most DeFi Wrapper components. It is **self-administered**, meaning role changes and privileged actions should go through timelocked proposals.

run-on-lido/stvaults/building-guides/pooled-staking-product/withdrawals.md

@@ -16,7 +16,7 @@ This page explains how to operate withdrawals for a pooled staking product (DeFi
 
 ## Automation
 
-You can use CLI to automatically submit reports and finalize(if possible) withdrawals for the pool. Finalization requires private key of address holding `FINALIZE_ROLE`. This command will exit on errors and needs to be run with a process manager (missed reports will be checked on start)
+You can use CLI to automatically submit reports and finalize (if possible) withdrawals for the pool. Finalization requires private key of address holding `FINALIZE_ROLE`. This command will exit on errors and needs to be run with a process manager (missed reports will be checked on start)
 
 ```bash
 # Check --help for extra configuration and HTTP callbacks