Lesson 2 of 12 · Beginner

Headings give a note its skeleton

One hash per level, in order, with a space after the marks.

In this lesson you will learn heading syntax from # to ######, how to keep levels in a logical order, and the two mistakes that silently flatten a document.

Syntax

# Title (level 1)
## Section (level 2)
### Subsection (level 3)
#### Level 4
##### Level 5
###### Level 6

Most notes need only the first three levels: one # title, ## sections, ### subsections. Deeper levels exist for long documents, not everyday notes.

A real example

# Project notes

## Introduction

What this project is and why it matters.

## Tasks

### This week

- [ ] Draft the proposal

### Later

- [ ] Schedule the review

Two mistakes to avoid

Skipping levels — jumping from # straight to ###. Readers and assistive tools expect each level to nest inside the previous one; a skipped level reads as a broken outline.
Forgetting the space — ##Tasks without the space after the marks is not a heading, it renders as literal text. Always write ## Tasks.

A related habit: keep exactly one level-1 heading per note and let it match the note's subject. Everything else hangs below it.

Exercise

Project notes

Introduction

Tasks

Fix it in the new note: turn the three lines into an H1 followed by two H2 sections, then check the outline in Preview — or use Split to watch both.

Try this exercise in Typehall

New to Typehall? Edit the Markdown in the new note, then choose Preview to see the rendered result, or Split to edit and preview at the same time. How the Markdown editor works. Tip: Split works especially well with Focus enabled, giving the editor and rendered preview more room.

Next, add emphasis inside the structure: Bold and italic.

Learn Markdown course index — all 12 lessons in order.