docs: migrate remaining 'staking' terms to 'bonding'

[yigitdot]

Problem

The staking → bonding terminology migration started in #145 is incomplete. It was originally filed as a glossary-only miss, but an audit (during #187) shows the old staking terminology still survives in one glossary cell and across several other docs + site-copy locations — so the premise that "the rest of the docs were migrated in #145" does not hold.

The economic mechanism is otherwise consistently called bond / bonding / bonded (the contract is CapacityBond; the glossary term is Bond), so these stragglers read as drift.

Rule: migrate technical protocol terms (stake → bond, staked → bonded, staking → bonding). Preserve stake only where it is idiomatic ("having a stake", "skin in the game"), not as a protocol verb/noun.

Remaining occurrences

Glossary — 1 cell left

The other four cells this issue originally listed are already migrated. Only one remains:

Term	Current	Updated
Client (docs/overview/glossary.mdx:12)	"No stake, no gossip publish."	"No bond, no gossip publish."

Non-glossary docs + site copy

File:line	Current text
docs/protocol/network.mdx:8	"All staked nodes form a flat mesh"
docs/protocol/network.mdx:16	"on-chain staking registry", "every staked node is slashable"
docs/protocol/reputation.mdx:8	"signed gossip reports from staked nodes"
docs/protocol/reputation.mdx:10	"Only staked nodes may submit gossip reports"
docs/protocol/reputation.mdx:20	"re-staking under a new identity"
docs/protocol/takedown.mdx:45	"requires fresh stake under a new identity", "spin up a new operator, restake, re-register"
docs/overview/introduction.mdx:6	"staked independent nodes cache content"
docs/overview/how-it-works.mdx:71	"signed gossip from staked nodes"
docs/docs.json:5	site description — "staked nodes cache and serve content"

Apply the same stake → bond / staked → bonded / staking → bonding substitution (e.g. "bonding registry", "bonded node", "re-bonding", "fresh bond", "re-bond"). None of the above are idiomatic uses.

---

Originally flagged by @gemini-code-assist[bot] in #145 (comment); re-surfaced on network.mdx:16 and scope-corrected in #187 (comment).

[github-actions]

🎯 Agentic Issue Triage

This is a documentation task to align the glossary with the protocol's renamed terminology: stake/staking → bond/bonding.

The proposed glossary table in the issue body already reflects the target state — the task is to find any remaining occurrences of the old terminology in the docs and update them.

📋 Sub-tasks checklist

• Search content/ and docs/ for occurrences of stake, staked, staking used as technical protocol terms (not idiomatic expressions like "having a stake")
• Update glossary entries to use bond, bonded, bonding per the table in the issue body
• Preserve idiomatic uses of "stake" (e.g. "skin-in-the-game", "having a stake in") — do not rename those
• Verify the updated glossary table renders correctly
• Check TOKEN definition: ensure "bonding token" language is consistent throughout

🔍 Debugging / search strategy

Run a quick ripgrep sweep to find candidates:

# Find protocol-term uses of stake/staking in docs
rg -i '\bstake[sd]?\b|\bstaking\b' content/ docs/ --glob '*.mdx' --glob '*.md'

Then review each hit to distinguish technical uses (rename) from idiomatic uses (keep).

i️ Context

• Originally surfaced by @gemini-code-assist[bot] in PR docs: sync protocol docs to canonical decdn/decdn state #145 review (discussion_r3328864546)
• The glossary table in the issue body already shows the desired end-state — use it as the reference
• Only docs/ content is relevant here (Mintlify source at docs.decdn.org); the main website (app/, components/, content/blog/) likely does not contain this glossary

Generated by Agentic Triage for issue #146 · ● 1.3M · ◷

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/issue-triage.md@c7d030cd6d4607b90d9ac3ffc8b24aff4f251632