Fix USDT0 naming and FAQ formatting#32
Closed
probablyangg wants to merge 1 commit into
Closed
Conversation
Contributor
Styleguide check✓ 132 en pages — 0 blocking, 11 warnings docs/pages/en/explanation/autobahn.mdxdocs/pages/en/explanation/consensus.mdx
docs/pages/en/explanation/ethereum-compatibility.mdx
docs/pages/en/how-to/monitor-node.mdx
docs/pages/en/how-to/troubleshoot-node.mdx
docs/pages/en/reference/indexers.mdx
docs/pages/en/reference/ramps.mdx
docs/pages/en/reference/system-transactions-api.mdx
docs/pages/en/reference/wallets.mdxEnforced by |
Member
Author
|
closes BIZ-49 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
The FAQ questions were plain bold paragraphs, which gave the section weak visual hierarchy and no question-level anchors. Several navigation labels had also been mechanically title-cased into forms such as
Usdt0, which does not preserve the USDT0 brand name.This addresses BIZ-49 and the related docs feedback in Slack.
Impact
Readers get a clearer FAQ and consistent USDT0 naming across the affected page, navigation, and cross-links. The style guide now records the conventions that prevent the same drift in future edits.
Validation
npm run checkThe existing advisory style warnings remain unchanged. Changed English pages are expected to show stale translation notices until the PR translation workflow refreshes the generated Chinese and Korean files.