WIP: Improve docs metadata and SEO

[rodincave]

Summary

• Apply documentation manifesto casing and terminology updates across docs pages
• Improve MDX frontmatter so docs pages have unique, specific SEO titles and descriptions
• Prefer MCP Apps views wording in API reference metadata
• Fix typos and grammar issues found during the docs pass, including GitHub, VS Code, HTTP article usage, and telemetry wording

Validation

• Custom metadata audit: 67 MDX pages checked, 0 issues
• pnpm --dir docs lint
• git diff --check

Notes

• It looks like a long PR but it's only content!

Greptile Summary

This is a docs-only pass across 67 MDX pages improving SEO metadata and applying consistent terminology and casing rules throughout the Skybridge documentation.

• Frontmatter metadata: Every page receives a unique, keyword-rich description (and keywords on the two top-level pages) replacing generic one-liners, with no changes to routing or navigation structure.
• Terminology and casing: "VSCode" → "VS Code", "Github" → "GitHub", "a HTTP" → "an HTTP", "MCP Clients/Servers" → "MCP clients/servers", "Personal identifiable information" → "Personally identifiable information", and sentence-cased headings throughout.
• Prose polish: Telemetry opt-out instructions are simplified, one word-order fix in telemetry.mdx ("read from and write to"), and a handful of minor grammar improvements across the guides.

Confidence Score: 5/5

Pure documentation content changes with no functional code, no broken links, and no navigation structure modifications — safe to merge.

All 67 changed files are MDX documentation pages. Every change is limited to frontmatter metadata (title, description, keywords) and prose copy — casing fixes, grammar corrections, and terminology standardisation. There is no executable code, no schema changes, and no routing or sidebar structure touched.

No files require special attention.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
docs/telemetry.mdx:73
Using the singular "environment variable" when listing two distinct variables is mildly ambiguous — a reader could interpret it as needing to set both rather than choosing one. The previous plural form was clearer.

```suggestion
- setting the `SKYBRIDGE_TELEMETRY_DISABLED=1` or `DO_NOT_TRACK=1` environment variables
```

_{Reviews (2): Last reviewed commit: "Apply suggestions from code review" | Re-trigger Greptile}

[harijoe]

I don't really get what host-aware means, neither embedded UI, and user workflows

[rodincave]

yea this one was a bit hallucinated!

Open external URLs safely from inside your MCP Apps views

Better?

[harijoe]

AI hosts ?

[rodincave]

yes we can remove the AI hosts

Read and control MCP Apps view display modes such as inline, fullscreen, and picture-in-picture across supported MCP clients.

[harijoe]

I'm not sure about the ai hosts terminology

[rodincave]

Register MCP tools in Skybridge, bind them to React view ressources, configure tool metadata, and return structured content for MCP clients.
?