fix(run-validator): apply review feedback and few corrections

ecosystem/nodes/cpp/run-validator.mdx

@@ -20,13 +20,13 @@ This guide explains how to run a validator TON node with MyTonCtrl from scratch.
 
 ### 1.1 Maintain costs and expenses
 
-- 200 TON per month on the validator hot wallet for its operational transactions.
-- Validator deposit stake [700 000 TON \~ 4 000 000 TON](/ecosystem/nodes/cpp/run-validator#step-4:-set-optimal-stake-for-validator).
+- 150 TON per month on the validator hot wallet for its operational transactions.
+- Validator deposit stake [700K–2M TON per round](/ecosystem/nodes/cpp/run-validator#step-4:-set-optimal-stake-for-validator).
 - 100 TB/month traffic at a peak load.
 
 ### 1.2 Minimal hardware requirements
 
-- 16-core CPU (for example, Intel Xeon E-2388G or equivalent)
+- 8-core / 16-thread CPU (for example, Intel Xeon E-2388G or equivalent)
 - 128 GB RAM
 - 2 × 1.92 TB NVMe SSD, each with 250,000+ read IOPS and 83,000+ write IOPS
 - 1 Gbit/s network connectivity
@@ -179,7 +179,7 @@ sudo apt install -y speedtest-cli
 speedtest-cli
 ```
 
-Ensure download and upload speeds meet the [1 Gbit/s requirement](/ecosystem/nodes/cpp/run-validator#1-2-minimal-hardware-requirements).
+Verify that the network throughput is sufficient for the validator workload.
 
 ### 1.8 Harden server security
 
@@ -333,6 +333,13 @@ Run the validator installation. Installation takes approximately 20 minutes:
      cp -r /var/ton-work/db_old/keyring /var/ton-work/db/keyring
      sudo chown -R validator:validator /var/ton-work/db
      ```
+
+  1. Start the services again:
+
+     ```bash
+     sudo systemctl start validator.service
+     sudo systemctl start mytoncore.service
+     ```
 </Accordion>
 
 ### 2.3 Verify status results
@@ -474,7 +481,7 @@ Explore validator wallet by address with [Tonviewer](https://tonviewer.com/):
   Ensure precise handling of operations, carefully verifying the addresses for `single_nominator_pool`, `owner_address`, and `validator_wallet`. Any incorrect deposit processing may result in the permanent and unrecoverable loss of funds.
 </Aside>
 
-Credit the validator wallet. Ensure that at least 200 TON per month is available in the validator’s wallet to cover operational fees.
+Credit the validator wallet. Ensure that at least 150 TON per month is available in the validator’s wallet to cover operational fees.
 
 <Image
   src="/resources/images/nodes/run-validator/run-validator-9.png"
@@ -812,7 +819,7 @@ Make sure pair stakes are appropriately circulated, then focus on monitoring val
 
 ### 5.1 Fund the validator hot wallet
 
-Keep at least 200 TON on the validator hot wallet. This balance covers operational fees for approximately one month.
+Keep at least 450 TON on the validator hot wallet. This should be enough to cover operational fees for approximately 3 months.
 
 To check the current balance:
 
@@ -930,8 +937,8 @@ Check the following indicators:
 
 | Indicator                        | Expected value                          |
 | -------------------------------- | --------------------------------------- |
-| Local validator out of sync      | Less than 20 seconds                    |
-| Masterchain out of sync          | Less than 20 seconds                    |
+| Local validator out of sync      | Less than 5 seconds                     |
+| Masterchain out of sync          | Less than 5 seconds                     |
 | Validator efficiency             | Above 90%                               |
 | Validator index                  | Visible in status output                |
 | Validator participation position | Between 200 and 250 for optimal staking |
@@ -940,8 +947,6 @@ Check the following indicators:
   Validator efficiency may show 0% at the beginning of a cycle until the validator signs its first blocks. This is normal behavior.
 </Aside>
 
-Confirm that the validator participates in elections and recovers stakes on time by monitoring the pool balance in a [blockchain explorer](https://tonviewer.com/).
-
 Confirm that the validator participates in elections and recovers stakes on time by checking the pool balance in a [blockchain explorer](/ecosystem/explorers/overview). For greater observability, [set up the monitoring](/ecosystem/nodes/cpp/run-validator#5-7-set-up-monitoring) of various validator metrics.
 
 ## Troubleshoot common issues
@@ -955,7 +960,7 @@ Confirm that the validator participates in elections and recovers stakes on time
 
 ### Validator efficiency is below 90%
 
-- Confirm the node is fully synchronized (`Local validator out of sync` \< 20).
+- Confirm the node is fully synchronized (`Local validator out of sync` must be less than 5 seconds).
 - Check disk performance. Slow storage is the most common cause of low efficiency.
 - Verify that no other resource-intensive processes compete for CPU or RAM.
 - Review hardware against [minimum requirements](/ecosystem/nodes/cpp/run-validator#1-2-minimal-hardware-requirements).