Skip to content

Conversation

@aigerimu
Copy link
Contributor

fixes #936

@aigerimu aigerimu marked this pull request as draft October 22, 2025 19:50
@github-actions
Copy link

To fix the formatting issues:

  1. Install necessary dependencies: npm ci
  2. Then, run this command:
npx remark -o --silent --silently-ignore ecosystem/node/overview.mdx 

@aigerimu
Copy link
Contributor Author

@aigerimu include ton repo

@github-actions
Copy link

Thanks for the docs updates around the node overview. A couple of high‑severity anchor issues need fixes before merge.

Findings (2)

High (2)

[HIGH] Broken internal anchor for “Single nominator”

Location:

| [Single nominator](/ecosystem/node/overview#liquid-staking) | In this mode, the smart contract accepts stakes from a single user and operates a validator on the user’s behalf, distributing rewards securely using a cold wallet. |

Description:
The “Single nominator” table entry links to #liquid-staking, which targets a different section. The correct target is the “Single nominator pool” section on this page (ecosystem/node/overview.mdx:46), whose slug is #single-nominator-pool. Broken internal anchors are release‑blocking per the style guide.

Suggestion:

- |    [Single nominator](/ecosystem/node/overview#liquid-staking)    | In this mode, the smart contract accepts stakes from a single user and operates a validator on the user’s behalf, distributing rewards securely using a cold wallet.                                                                                                                                                                                              |
+ |    [Single nominator](/ecosystem/node/overview#single-nominator-pool)    | In this mode, the smart contract accepts stakes from a single user and operates a validator on the user’s behalf, distributing rewards securely using a cold wallet.                                                                                                                                                                                              |

[HIGH] Broken internal anchor to config parameter 16

Location:

Validator nodes or validators are the TON network participants who propose new blocks and verify transactions according to TON's [_proof-of-stake_](https://en.wikipedia.org/wiki/Proof_of_stake) mechanism. The top 400 validators are selected based on network [configuration parameter](/foundations/config#param-16%3A-validators-limits). Validators receive rewards for validation.

Description:
The link to the configuration reference uses an encoded colon in the anchor (#param-16%3A-validators-limits), which does not match the slug generated for the target heading “## Param 16: validators limits” on the referenced page. The correct slug drops punctuation and uses hyphens: #param-16-validators-limits. Broken/missing anchors are release‑blocking per the style guide.

Suggestion:

- Validator nodes or validators are the TON network participants who propose new blocks and verify transactions according to TON's [_proof-of-stake_](https://en.wikipedia.org/wiki/Proof_of_stake) mechanism. The top 400 validators are selected based on network [configuration parameter](/foundations/config#param-16%3A-validators-limits). Validators receive rewards for validation.
+ Validator nodes or validators are the TON network participants who propose new blocks and verify transactions according to TON's [_proof-of-stake_](https://en.wikipedia.org/wiki/Proof_of_stake) mechanism. The top 400 validators are selected based on network [configuration parameter](/foundations/config#param-16-validators-limits). Validators receive rewards for validation.

@github-actions
Copy link

To fix the formatting issues:

  1. Install necessary dependencies: npm ci
  2. Then, run this command:
npx remark -o --silent --silently-ignore ecosystem/node/overview.mdx 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Ecosystem > Node > Overview] Improve article

3 participants