# Style your Markdown notes

Use structure and a small amount of emphasis to make a note easy to scan. The saved document remains Markdown text, so its meaning should survive in another editor.

## Establish a hierarchy

Use `#` for the main subject, `##` for sections and `###` for subsections. Keep heading levels consistent instead of selecting them only for their size. Separate paragraphs with blank lines.

```markdown
# Release review

## Decision
The draft is ready for another review.

## Open question
Who confirms the final date?
```

Use `**bold**` for a short important phrase and `*italic*` for light emphasis. Avoid making whole paragraphs bold. Use backticks for literal commands and filenames.

## Understand the editor

Ouros styles headings, emphasis, links, quotes, lists and code inside the editable page. Markers can be concealed away from the active line and return while editing. This is not a separate page-layout or typography export tool.

There is no need to insert HTML, custom CSS or another app's Markdown extensions to write a readable note. Unsupported syntax can remain literal text.

## Review before sharing

Read the document from top to bottom, save it and reveal the file. Open it in the destination reader to check its interpretation. The same source can use different fonts and spacing in another application.

See [preview, copy and export](/docs/markdown/preview-copy-and-export) for moving the text or file.