feat(internal-infra): mdx and markdown formatter setup

[novusnota]

Closes #169.

Why not Prettier? Here's a brief explanation from the Docusaurus's docs:

And this is a link by the end of it: https://github.com/orgs/mdx-js/discussions/2067

In short, remark with necessary plugins and some tweaks in configuration works better than prettier. And biome, the uprising competitor of prettier, cannot even format regular Markdown yet, not to say of MDX.

That said, we might bring prettier for formatting non-mdx files, such as the files in the snippets/ directory.

[github-actions]

Thanks for the updates across the docs, especially in TON Connect, analytics, TMA Mate hosting, and TVM instructions. A few precise edits are needed to fix a link and tighten style/clarity.

Findings (5)

Medium (4)

Click to expand

[MEDIUM] Escaped reference link renders as plain text (broken link)

Location:

mintlify-ton-docs/ecosystem/ton-connect/walletkit/native-web.mdx

Line 56 in 10cafb3

For this option, you can deploy the \[official TON Connect Bridge implementation]\[bridge].

Description:
This escapes the reference link text so it renders literally, and the [bridge] reference is not defined in the file. Readers see plain text instead of a link.

Suggestion:
Unescape the link and define the reference.

-For this option, you can deploy the \[official TON Connect Bridge implementation]\[bridge].
+For this option, you can deploy the [official TON Connect Bridge implementation][bridge].

Add a reference definition near the end of the file:

[bridge]: https://github.com/ton-blockchain/ton-connect/blob/main/bridge.md

[MEDIUM] “etc.” used in a procedural list item

Location:

mintlify-ton-docs/ecosystem/ton-connect/walletkit/native-web.mdx

Line 62 in 10cafb3

3. Configure your infrastructure (load balancers, SSL certificates, etc.)

Description:
Using “etc.” in a procedure is discouraged because it’s open‑ended and ambiguous. Prefer closed examples or “for example” phrasing.

Suggestion:
Replace with a closed example list.

-3. Configure your infrastructure (load balancers, SSL certificates, etc.)
+3. Configure your infrastructure (for example, load balancers and SSL certificates)

[MEDIUM] Unclear phrasing “from the Mate config prior”

Location:

mintlify-ton-docs/ecosystem/tma/mate/hosting.mdx

Lines 263 to 264 in 10cafb3

	# Both of these commands will use the options
	# from the Mate config prior

Description:
“Prior” reads as legalistic and interrupts scanability in the inline comment. Plain, concise wording improves readability.

Suggestion:
Replace with a single, clear sentence.

-# Both of these commands will use the options
-# from the Mate config prior
+# Both commands use options from the Mate config.

[MEDIUM] Banned filler words in reference descriptions (“simply”, “just”)

Location:

mintlify-ton-docs/tvm/instructions.mdx

Lines 733 to 739 in 10cafb3

	Description: Performs `EXECUTE` for `c` (i.e., _executes_ `c`), but only if integer `f` is non-zero. Otherwise simply discards both values.
	Category: cont\_conditional Cont Conditional
	#### `DF` IFNOT
	Fift: IFNOT
	Description: Executes continuation `c`, but only if integer `f` is zero. Otherwise simply discards both values.

Description:
Filler adverbs like “simply/just” reduce precision and are discouraged. Similar instances appear elsewhere in the diff (e.g., 3179, 3572, 3722).

Suggestion:
Remove filler adverbs and keep factual wording.

-Otherwise simply discards both values.
+Otherwise discards both values.

-or simply ''perform `c`, then `c'`''.
+or ''perform `c`, then `c'`''.

-If `i` does not fit into `n` bits, simply returns `D` `0` (''key not found, dictionary unmodified'').
+If `i` does not fit into `n` bits, returns `D` `0` (''key not found, dictionary unmodified'').

-Otherwise, just returns the old value `y` without changing the dictionary.
+Otherwise, returns the old value `y` without changing the dictionary.

Low (1)

Click to expand

[LOW] Missing Oxford comma in a three-item list

Location:

mintlify-ton-docs/ecosystem/analytics.mdx

Lines 36 to 37 in 10cafb3

	- [NFT events](https://dune.com/queries?category=canonical\&namespace=ton\&id=ton.nft_events) — comprehensive source of NFT-related data including
	sales, transfers and mints.

Description:
The list omits the serial comma in “sales, transfers and mints.” The style guide requires the Oxford comma for clarity.

Suggestion:
Insert the serial comma.

-  sales, transfers and mints.
+  sales, transfers, and mints.

[verytactical]

Choice of technology is understandable.

Obviously we can't review that manually :)