# Code blocks, quotes, and technical notes

Keep commands and quoted material distinct from your own explanation. Code in Notes is text; saving it does not execute it.

## Use inline code

Surround a short command, filename or identifier with backticks, such as `pwd` or `notes.md`. The editor uses a code face for the text between the markers.

## Keep a longer example together

Use three backticks on their own line before and after a block:

````markdown
```sh
pwd
```
````

The optional `sh` label is useful in the saved source and other Markdown readers. Ouros styles fenced code as monospaced text; do not assume language-specific syntax highlighting or an embedded Run button.

## Quote a statement

```markdown
> Delivery depends on the final review.

My follow-up: ask who owns that review.
```

Use `>` at the start of each quoted paragraph. Add the speaker, date or source in the note when it matters. A quotation marker by itself does not establish attribution.

## Reuse a command carefully

Review a copied command in its destination terminal before pressing Return. Check paths, arguments and any action that changes files. A code block can contain an example, an old command or untrusted text.

Save and reveal the file to check the literal backticks and quote markers. See [your first command](/docs/terminals-and-files/first-command) for a harmless shell exercise.