# Use contractions (EK00033)

import { Aside, Badge } from '@astrojs/starlight/components';

Contractions such as "can't" and "doesn't" give documentation a conversational tone that matches how people speak and read. EkLine flags full verb forms that read more naturally as contractions and suggests the contracted form (rule EK00033).

## Why use contractions in documentation?

Contractions make writing sound approachable rather than stiff. "You can't undo this" reads the way a person talks, while "You cannot undo this" feels formal and distant. A friendly, consistent voice keeps readers engaged and signals that the documentation was written for them, not for a legal filing.

## What EkLine flags

EK00033 detects full forms such as `do not`, `is not`, and `cannot` that read more naturally as contractions.

- ❌ **Incorrect:** You cannot undo this.
- ✅ **Correct:** You can't undo this.
- ❌ **Incorrect:** The file does not exist.
- ✅ **Correct:** The file doesn't exist.

## How to fix

Replace the full form with its contraction. Change "cannot" to "can't" and "does not" to "doesn't".

<Aside type="note">
Some contexts call for full forms — for example, a warning that needs extra emphasis, or a term used literally. In those cases, keep the full form and ignore the rule for that line.
</Aside>

## FAQ

### Are contractions acceptable in technical documentation?

Yes. Contractions give technical documentation an approachable, conversational voice, and most modern style guides encourage them. Reserve full forms for cases that need extra emphasis.

### When should you avoid contractions?

Keep the full form when a warning needs emphasis or when a term is used literally, such as "You cannot recover deleted data." Everywhere else, contractions read more naturally.

## Rule details

| Property | Value |
|----------|-------|
| Rule ID | `EK00033` |
| Category | Tone and voice |
| Default severity | <Badge text="Warning" variant="caution" /> |
| Enabled by default | Yes |

## Ignore this rule

To keep a full form on one line, add an inline comment with a reason:

```markdown
<!-- ekline-ignore-next-line EK00033 -- emphasis in a warning -->
You cannot recover deleted data.
```

To disable the rule across your project, add it to the `ignore` list in your [configuration file](/reviewer/configuration/ignoring-rules/#ignore).

## Related rules

- [EK00005](/reviewer/rules/present-tense/) — Prefer present tense over future tense
- [EK00047](/reviewer/rules/first-person-pronouns/) — Limit first-person pronouns