# Code and Code Blocks > [!abstract] What this note is > How to show code, commands, or *any text that must not be reformatted* — including how to talk about Markdown inside Markdown without it rendering. ## Inline code Wrap text in single backticks for a short snippet inside a sentence: ```markdown Run `git status` before you commit. ``` Renders as: Run `git status` before you commit. ## Code blocks Three backticks (a "fence") on the lines before and after: ````markdown ``` anything in here renders exactly as typed *even this* stays plain ``` ```` ## Syntax highlighting Name the language after the opening fence: ````markdown ```python def hatch(egg): return "chicken" ``` ```` Common language tags: `python`, `javascript`, `bash`, `json`, `yaml`, `markdown`, `html`, `css`, `sql`. ## Why code blocks matter beyond code Anything inside a fence is **protected from Markdown itself**. That's why this vault's reference notes can *show* syntax like `[[wikilinks]]` and `2026-07-10` without Obsidian rendering or Templater executing them. When you need to display raw syntax, fence it. > [!tip] Fences inside fences > To show a code block *inside* a code block (like this note does), use four backticks for the outer fence. ## Related - [[Markdown Basics]] - [[Markdown Reference Index]]