A product manager is writing a lengthy issue that describes a new feature. The issue includes background context, acceptance criteria, and open questions. She wants readers to quickly scan and jump between these distinct sections when the issue renders on GitHub. Which Markdown technique should she use to structure the issue this way?