A glossary generated by AI often looks simple: one term, followed by one explanation. After conversion to Word, however, the terms may lose visual distinction, long defin...
A multilevel Markdown list can look correct in an editor and still flatten, restart, or continue incorrectly after conversion to Word. Child items may become top-level bu...
AI-generated Markdown often contains decorative elements that work in a chat window but weaken a professional Word document. Emoji headings, repeated horizontal rules, ch...
A Markdown document may look well organized in an editor and still produce unexpected pagination in Word. A chapter may begin halfway down a page, a heading may be left a...
A Mermaid diagram can render correctly in a Markdown preview and still become too small, too tall, blurry, or partially clipped after conversion to Word. The diagram may...
AI-generated reports often contain headings that look acceptable in chat but create a weak Word document. Several sections may use the same heading level, H2 may jump dir...
The same Markdown source can produce noticeably different Word documents depending on the selected template. Heading spacing, page breaks, table borders, code styling, ca...
A document can contain correctly formatted headings, figures, tables, and equations while its internal references still fail. Instead of “see Figure 3” or “refer to Secti...
Markdown footnotes are easy to write, but they can become confusing after conversion to Word. A reference may remain as [^1], numbering may change, repeated references ma...
A fenced code block may look correct in a Markdown editor and still become difficult to read after conversion to Word. Indentation can shift, long commands may extend bey...
