docs: remove em dashes and establish writing style guidelines (#980)

- Removed em dashes from mcp-server.mdx and CLAUDE.md
- Added Documentation Writing Style section to CLAUDE.md with guidelines for consistency across docs

Author: brendan-kellam

CLAUDE.md

@@ -184,7 +184,7 @@ export const GET = apiHandler(async (request: NextRequest) => {
 
 ## Next.js Router Navigation
 
-Do NOT call `router.refresh()` immediately after `router.push()`. In Next.js 16, the prefetch cache and navigation system was completely rewritten, and calling `router.refresh()` right after `router.push()` creates a race condition — the refresh invalidates the cache and can interrupt the in-flight navigation, leaving the page stuck or not loading.
+Do NOT call `router.refresh()` immediately after `router.push()`. In Next.js 16, the prefetch cache and navigation system was completely rewritten, and calling `router.refresh()` right after `router.push()` creates a race condition. The refresh invalidates the cache and can interrupt the in-flight navigation, leaving the page stuck or not loading.
 
 ```ts
 // Bad - router.refresh() races with router.push() in Next.js 16
@@ -197,6 +197,18 @@ router.push(url); // ✅
 
 If you need to refresh server component data after a mutation, use the server-side `refresh()` from `next/cache` in a Server Action instead of `router.refresh()` on the client.
 
+## Documentation Writing Style
+
+When writing or editing `.mdx` files in `docs/`:
+
+- Do NOT use em dashes (`—`). Use periods to break sentences, commas, or parentheses instead.
+- Write in second person ("you") and present tense.
+- Keep sentences short and direct. Lead with what the user needs to know.
+- Use bold for UI elements and key terms (e.g., **Settings → API Keys**).
+- Use inline code for technical values, flags, and identifiers (e.g., `REPO_READ`).
+- Prefer short paragraphs (1-3 sentences). Use bullet lists to break up dense information.
+- Use tables for parameter documentation.
+
 ## Docs Images
 
 Images added to `.mdx` files in `docs/` should be wrapped in a `<Frame>` component:

docs/docs/features/mcp-server.mdx

@@ -281,7 +281,7 @@ Regardless of which method you use, all MCP requests are scoped to the associate
 
 <LicenseKeyRequired feature="OAuth" />
 
-Sourcebot implements an OAuth 2.0 authorization server with support for dynamic client registration (RFC 7591). This means MCP clients can register themselves automatically without any manual setup — just point your client at the MCP endpoint and it will handle the full authorization flow, prompting you to log in and approve access in your browser the first time you connect. No API key or manual token management is required.
+Sourcebot implements an OAuth 2.0 authorization server with support for dynamic client registration (RFC 7591). This means MCP clients can register themselves automatically without any manual setup. Just point your client at the MCP endpoint and it will handle the full authorization flow, prompting you to log in and approve access in your browser the first time you connect. No API key or manual token management is required.
 
 Once authorized, Sourcebot issues a short-lived access token (valid for 1 hour) and a refresh token (valid for 90 days). The MCP client handles token refresh automatically, so you stay connected without needing to re-authorize.