The “Review notes” heading appears in the terminal-style block above it. A missing closing fence can make the renderer treat the remaining Markdown as code.

Find the opening fence and the intended end

In source view, find the line starting the fenced sample. Check for a closing line with the same fence character and at least as many characters as the opener. In this example the sample ends after status: ready:

```text
status: ready
```

## Review notes

An example source shows a text fence with no closing line before the Review notes heading.

Illustrated diagnosis. Check where ordinary text first starts appearing inside the code block.

Verify the repaired boundary

Open the preview. Confirm the code block contains the status line and “Review notes” is outside it as a heading. If the note is nested in a list or quote, also check indentation and the surrounding container. Inspect the next section to make sure the correction did not introduce a second accidental code block.

The corrected source adds a closing fence and the preview shows Review notes as a heading.

Illustrated repair. Check the code and the next section in the preview.

CommonMark’s fence rules.