Common Markdown Mistakes
The small errors that break rendering most often: missing blank lines, broken fences, and mismatched emphasis.
The missing blank line
The single most common mistake. Two paragraphs on adjacent lines with no blank line between them are joined into one. A list pressed directly against a paragraph may not render as a list. A heading with no blank line above it can be swallowed into the paragraph above. The fix is mechanical: put a blank line before and after every block-level element.
Unclosed emphasis
An asterisk or underscore that opens emphasis but is never closed leaves the rest of the line, or the rest of the document, in the wrong style. A stray asterisk in a multiplication sign or a wildcard can start emphasis you did not intend. When text looks italic that should not be, count the emphasis markers and make sure they pair.
Broken code fences
A fenced code block needs three backticks above and three below. If the opening fence is closed early, or one fence is missing, the code block runs into the following prose or the prose is swallowed into the code. If your document suddenly turns monospaced from a certain point, a fence is almost always the cause.
Indented lists that are not lists
A line that begins with spaces and a dash can be read as a nested list item even when you meant a plain bullet, or as a code block if the indentation is deep enough. Keep list indentation shallow and consistent: two or four spaces for a nested level, applied the same way every time. When a list looks wrong, check the indentation before rewriting it.
Read the rendered output, not the source
The source of a link and what a reader sees are not the same thing. A missing space, an extra bracket or a stray character between the label and the address leaves the link literal — it looks like text, not a clickable target. Open the rendered page and click every link before you publish a document that will be read by someone else. It takes ten seconds and it is the only check that catches the mistake the source will happily hide.
A whole document in one paragraph
A document with no blank lines anywhere renders as one long block of text, because the renderer joins every adjacent line into the same paragraph. The text is all there, but nobody can read it. This is the failure people blame on the renderer when the real cause is the source: the format is doing exactly what it was told. The fix is not a setting, it is a habit — a blank line between every block.
Fixing it in the right place
When something renders wrong, resist the urge to restructure the whole document. Find the first line that renders incorrectly and work backwards: is there a blank line missing, an unclosed marker, or a fence that never closed? Nine times out of ten the fix is one line. Rewriting the section around it only hides the cause and makes the next edit harder.