expo-writing-stylelisted

# Expo Writing Style Apply Expo's documentation writing style and component conventions when authoring or reviewing content for `expo/docs/pages/`. **Apply these conventions while drafting, not as a cleanup pass.** ## When to Use - Drafting new docs pages (`.mdx` under `expo/docs/pages/`) - Editing existing prose for tone, voice, or clarity - Picking the right MDX component (`Terminal` vs. a plain code block, `Step` vs. a numbered list, `Tabs` vs. duplicated snippets) - Reviewing PRs to expo/docs/ - Translating draft prose into Expo's voice ## How to apply Two reference files live next to this skill. Read the one that matches the task. When a change touches both prose and components, consult both. - **`../../../references/expo-docs-style-guide.md`**: prose rules. Voice, tone, punctuation, formatting, glossary, anti-patterns, and Expo-specific gotchas with concrete before/after examples. - **`../../../references/expo-docs-components.md`**: MDX component catalog. Mandatory-usage rules, prop tables, minimal examples, and gotchas for `Terminal`, `Tabs`, `Step`, `Prerequisites`, `Collapsible`, `FAQ`, `BoxLink`, `SnackInline`, `ContentSpotlight`, `VideoBoxLink`, `APISection`, the `ConfigSection` trio, `AndroidPermissions` / `IOSPermissions`, `PlatformTags`, `ProgressTracker`, plus less common authoring components. For deterministic checks (Oxford commas, spelling), run Vale from `expo/docs/` via `pnpm lint-prose` or `.vale/bin/vale`. The references cover what Vale cannot se