A corrected instruction can look finished in the preview while the file on disk still contains its old wording. Checking both states avoids sending the wrong version of an otherwise readable note.
Open a small Markdown source file
Save this original practice note as packing-note.md:
# Packing the display kit
Use the case labeled `DISPLAY-4`.
## Before collection
- Pack the stand in the long compartment.
- Put the adapter in the inner pocket.
| Item | Location |
| --- | --- |
| Printed labels | Front pocket |
| Spare cable | Inner pocket |
The kit, label, and locations are fictional practice details. Replace them before issuing a real packing instruction. The heading, list, code label, and table give the preview separate structures to render.
With the file active, toggle Live preview in the Coding tab. Confirm that the title appears as a heading, the two packing tasks remain separate, and each table item stays beside its location. UltraEdit documents GitHub Flavored Markdown rendering, including tables, in this view.
Trace a rendered sentence back to the source
Double-click a static element in the preview to jump to its source position. Use the kit label for a simple check: find DISPLAY-4 in the rendered note, jump to its source, and confirm that you reached the intended occurrence.
Change the fictional label to DISPLAY-5. The preview should update before you save. Now save the file, close and reopen it through your usual workflow, and confirm that the maintained source contains the intended label. Restore the original practice value if you are only testing the feature.
The documented source-position jump does not work for elements created dynamically by JavaScript. Use a static heading or paragraph when checking this navigation feature.
Change preview styling only after checking the source
The drop-down under Live preview offers rendering styles and an option to add or remove your own CSS stylesheets. These style options require the file to be syntax highlighted as Markdown. If the controls are absent, check the active file and its highlighting before changing a stylesheet.
A different preview style can change spacing or table appearance. It cannot supply a missing instruction. In the packing note, first confirm that “Spare cable” still maps to “Inner pocket”; adjust presentation only after that relationship is correct.
Review the destination as well as the editor
A local preview establishes how this editor rendered the source. If the note will live on GitHub, check it there too, including links and relative asset paths. GitHub Markdown checks explain that destination's behavior.
Keep the .md file as the maintained source unless the actual task requires an export. For a packing note, the final check is concrete: reopen the saved file, confirm the case label, and make sure the adapter's location remains unambiguous.