A command for generating a route file should sit under the step that uses it. If the fence starts at the left margin, the preview can split the instructions into separate blocks.

Indent the whole fence under the step text

In this example, the text starts after 1. , so use three spaces for the opening fence, the command and the closing fence. The command is an illustrative placeholder.

1. Generate the route file.

   ```text
   route-demo --output route.txt
   ```

2. Open the route file.

The opening fence, command and closing fence are indented three spaces under step 1.

Illustrated source. For this list marker, match the start of the step text.

Look at the nesting in the destination

The code block should be part of step 1. Step 2 should return to the original list margin. If you use a longer list marker, such as 10. , match that item’s content indentation. Preview it after copying the list into its final location.

The preview shows a code block within step 1 followed by step 2 at the list margin.

Illustrated nesting check. The example command stands in for a real project command.

CommonMark list item indentation rules