docs: fix Chinese and Japanese desktop troubleshooting formatting - #337
Merged
Conversation
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.
Chinese and Japanese Desktop App troubleshooting labels display literal
**instead of bold text because the full-width colon sits inside the bold span immediately before the body text. Move the colon outside the bold span in all ten affected entries.Validation: scanned 315 website and README documents across all seven languages; verified all five troubleshooting labels render as bold in every language's MDX and production HTML; passed the full seven-language website build after clearing stale build caches,
make lint, andgit diff --check.The repository-wide Python formatting hook was skipped for this Markdown-only commit because it reformatted 60 unrelated Python files; those hook-generated changes were reverted.