feat(sub-second): add how to adopt sub-second finality page

[aigerimu]

closes #1983

[github-actions]

Thanks for the thorough work on ecosystem/subsecond.mdx; I’ve left several suggestions to align wording, formatting, and safety guidance with the docs conventions, so please apply the inline suggestions where they fit. Once updated, the document should read more consistently and be clearer for both UX and infrastructure readers.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
mintlify-ton-docs	🟢 Ready	View Preview	Mar 20, 2026, 9:45 PM

[it09]

Great work, minor comments

[novusnota]

It's ok to say that, as of now, tangible changes are being made only to the testnet. Yet this page should focus on instructing dApp and wallet devs on how to, well, adopt sub-second finality in their projects. Like, a) what's the status and expected outcome, and b) how to adapt to the changes, with steps or checklists to follow.

All lower-level details, even the name of the consensus protocol (Simplex aka "Catchain 2.0"), should be left to pages within "Blockchain foundations": see #1991 and so on.

@aigerimu @thekiba Let's keep that in mind when rewriting this page, wdyt? :)

[github-actions]

Thanks for the detailed work on ecosystem/subsecond.mdx: I’ve suggested several edits to tighten task-focused wording, numeric formatting, and references; please apply the inline suggestions. I also flagged one small dictionary tweak in resources/dictionaries/two-letter-words-ban.txt to keep unit usage consistent.

---

Per-comment submission: 25 posted, 1 failed.

Unposted inline comments (raw text):

• resources/dictionaries/two-letter-words-ban.txt:L1194-L1200

  [HIGH] Removal of !ms from two-letter banned words weakens unit consistency

  The dictionary change removes the !ms entry from two-letter-words-ban.txt, leaving other case variants like !Ms, !MS, and !mS. This file appears to configure banned two-letter tokens for style or spellchecking, and ms is used throughout the new documentation as a unit abbreviation for milliseconds, not as a standalone word. Allowing ms as an unbanned token increases the risk of inconsistent usage and conflicts with the unit style that treats ms as a numeric unit, not a normal word. Restoring !ms keeps unit formatting consistent and maintains the original enforcement behavior.

  !Mr  …(truncated)
  

[github-actions]

Thanks for the thorough work on ecosystem/subsecond.mdx and the sidebar wiring; I’ve left several suggestions to align the doc type, safety callouts, terminology, and media/structure details, so please apply the inline suggestions.

[github-actions]

[HIGH] Sidebar ordering may misrepresent mixed-content page type

The new ecosystem/subsecond entry is inserted directly before ecosystem/status and ecosystem/analytics within the same ecosystem group. Given that ecosystem/subsecond.mdx mixes explanation, integration guidance, and testing instructions (and currently uses a “How to …” title), its placement in the sidebar risks violating the style guide’s HIGH-severity rule to order docs as Explanation → How‑to → Reference within groups. Without clarifying the page’s type and adjusting its position, navigation may mislead readers about whether the page is a high-level overview, a how-to, or a reference.

Suggested change

	"ecosystem/subsecond",
	"ecosystem/status",
	"ecosystem/analytics",
	"ecosystem/status",
	"ecosystem/subsecond",
	"ecosystem/analytics",

Please leave a reaction 👍/👎 to this suggestion to improve future reviews for everyone!