Skip to content

docs: deep polish across all sections (typos, terminology, formatting)#189

Open
hongyi-chen wants to merge 5 commits into
mainfrom
docs/deep-polish
Open

docs: deep polish across all sections (typos, terminology, formatting)#189
hongyi-chen wants to merge 5 commits into
mainfrom
docs/deep-polish

Conversation

@hongyi-chen
Copy link
Copy Markdown
Collaborator

Summary

Deep, corrective polish across the entire Warp docs content set (src/content/docs/). This is a cleanup-only pass — typos, grammar, terminology consistency, and style-guide formatting — with no page rewrites, restructures, renames, or navigation/redirect changes.

The work was split across three parallel agents, each owning a disjoint set of directories, then merged into this branch:

  • agent-platform / getting-started / root — 43 files
  • terminal / code / knowledge-and-collaboration / enterprise — 75 files
  • guides / reference / support-and-community / changelog (changelog light-touch) — 63 files

Total: 181 files changed (+645 / -644).

Representative fixes

  • Terminology (per AGENTS.md + .agents/references/terminology.md): agent modeAgent Mode; GithubGitHub; MacOSmacOS; Blocklistdenylist; ambient agentcloud agent; Agent ModalityTerminal and Agent modes; Oz "programmable agent" → "programmable platform"; Streamable HTTPSStreamable HTTP; WezTerm/iTerm2/VoiceOver casing.
  • Formatting: Settings paths normalized to **Settings** > **X**; real clickable UI elements bolded; headers to sentence case (preserving feature/proper names); keyboard shortcuts into backticks with + separators; leftover GitBook   artifacts and escaped backticks removed; one mis-leveled :::danger:::caution.
  • Typos / real bugs: git push –set-upstream (en-dash) → --set-upstream; SHIFT-UP/SHIFT-UP keybinding → SHIFT-UP/SHIFT-DOWN; broken link slug nvdn/thefucknvbn/thefuck; malformed markdown link missing ]; Secret ReductionSecret Redaction; assorted a MCPan MCP, WarpsWarp's, etc.
  • Links: raw-URL anchor text replaced with descriptive text; a stale heading anchor and a wrong cross-reference fixed; trailing-slash normalization on a couple of internal links.

Related issues

None — proactive cleanup pass.

Validation

  • npm run build — ✅ 337 pages built, 0 errors.
  • npm run typecheck (astro check) — ✅ 0 errors (pre-existing TS deprecation hints in .astro/.tsx components only).
  • python3 .agents/skills/check_for_broken_links/check_links.py --internal-only — ✅ 0 broken internal links (2,907 checked).
  • python3 .agents/skills/style_lint/style_lint.py --all — actionable categories reduced (OZ-TERM 4→0, DEPRECATED 5→2, PRODUCT-CASING 17→2, HEADER-CASE 156→79). Remaining items are confirmed false positives or intentional keeps: proper-noun headers, defined-term acronyms (ZDR/SSO/BYOLLM), code identifiers and keyboard keys in backticks (Enter, .dmg, settings.toml, imagePullSecrets, status_message), and 217 judgment-based screenshot-maxWidth warnings (left per scope).
  • npm run lint (Trunk) not run — Trunk is not installed locally.

Screenshots

None — text-only changes.

Follow-ups

Items intentionally left for human review (out of polish scope or need a domain decision):

  • Product UI mismatch: secret-redaction.mdx keeps the literal UI label "Hide secrets in blocklist" — the product UI itself uses the deprecated "blocklist" term.
  • Wrong example content: the Linear "lean build" guide's step 2 prompt is a copy-paste of the gcloud-logs prompt; needs the correct prompt.
  • Factual inconsistencies to confirm (not guessed): cmd.exe support wording differs between supported-shells and migrate-from-windows-terminal; conversation-forking key differs between two pages; skill-directory precedence order differs between skills.mdx and skills-as-agents.mdx; subshells.mdx uses defaults update (likely should be defaults write).
  • Repo-wide consistency passes deferred (too broad for a polish): keyboard-combo notation (⌘+I vs CMD + I vs ⌘I), "Computer Use"/"Full Terminal Use" body casing vs lowercase page titles, and relative vs absolute docs.warp.dev cross-space link style.
  • Non-sequential section numbering in how-to-set-up-ollama.mdx and a GitHub MCP guide; a possibly-stray bullet in tabs-behavior.mdx.

Co-Authored-By: Oz oz-agent@warp.dev

hongyi-chen and others added 5 commits June 7, 2026 16:25
…changelog

Meaning-preserving copyedit across owned docs directories:
- Headers to sentence case (preserving proper feature names: Agent Mode,
  Codebase Context, Command Palette, Warp Drive, Code Review, Skills, etc.)
- Settings paths normalized to **Settings** > **X** (arrows -> bold + >)
- Keyboard shortcuts in backticks with + separator (Cmd+I, Ctrl+Shift+P);
  fixed ALL-CAPS combos (CTRL+SHIFT+C -> Ctrl+Shift+C)
- Terminology: agent-mode -> Agent Mode, Mac -> macOS, Github -> GitHub,
  ambient agent -> cloud agent, blocklist -> denylist, Secret Reduction ->
  Secret Redaction, codebase context -> Codebase Context
- UI buttons bolded (Apply Changes, Fast-Forward, Save)
- Raw-URL link anchors replaced with descriptive link text
- Fixed a stale anchor (#what-telemetry-data-are-you-collecting-and-why ->
  #what-telemetry-data-does-warp-collect-and-why)
- Typo fixes ("y you" -> "you", "Serve" -> "server", "t-short" -> "t-shirt",
  "commens"/"sumary" in example prompts)
- changelog: light touch only (Github -> GitHub casing typos)

Left intentionally: linter false positives (proper nouns, JSON field names
like status_message/detail, macOS app-bundle paths Contents/MacOS),
embedded sample WARP.md content, generated license body text, verbatim
error-message headers, and judgment-based screenshot-width warnings.

Co-Authored-By: Oz <oz-agent@warp.dev>
Meaning-preserving polish across agent-platform/, getting-started/, and the
root index.mdx/quickstart.mdx:

- Terminology: normalize "Third-Party CLI Agents" -> "Third-party CLI agents"
  and "Cloud Agents Overview" -> "Cloud Agents overview"; "Streamable HTTPS"
  -> "Streamable HTTP"; lowercase "git repository" -> "Git repository";
  "docker" -> "Docker"; "StackOverflow" -> "Stack Overflow"; "Large Language
  Model(s)" -> lowercase for consistency.
- Headings/titles: sentence-case generic titles (Keyboard shortcuts, Supported
  shells, Agent notifications, Integrations overview, Cloud providers); remove
  redundant bold inside headings.
- Formatting: bold settings paths and UI buttons/menu items instead of
  backticks/plain text; fix Shift-Tab -> Shift+Tab separator; remove GitBook
  artifacts (trailing/leading &#x20;, escaped backticks); add a missing blank
  line before a heading.
- Grammar/punctuation: "a MCP" -> "an MCP server"; "To add a multiple" -> "To
  add multiple"; missing periods; "bash, and zsh" -> "bash and zsh".
- Cross-references: fix an "environment" link that pointed to integration-setup
  instead of environments; add trailing slashes to two internal links;
  descriptive link text for fishshell.com.

Co-Authored-By: Oz <oz-agent@warp.dev>
Corrective, meaning-preserving polish: typos, grammar, terminology
(per glossary), header sentence-case, Settings-path and UI-element
formatting, callout types, and link-text quality.

Co-Authored-By: Oz <oz-agent@warp.dev>
Consolidates corrective polish of the Warp docs: typos, grammar, terminology
consistency, and style-guide formatting fixes across agent-platform, terminal,
code, knowledge-and-collaboration, enterprise, guides, reference,
support-and-community, getting-started, changelog, and root pages.

Co-Authored-By: Oz <oz-agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label Jun 7, 2026
@vercel
Copy link
Copy Markdown

vercel Bot commented Jun 7, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jun 7, 2026 11:56pm

Request Review

@oz-for-oss
Copy link
Copy Markdown
Contributor

oz-for-oss Bot commented Jun 7, 2026

@hongyi-chen

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

Copy link
Copy Markdown
Contributor

@oz-for-oss oz-for-oss Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This PR applies broad text-only polish across the docs, including terminology, Markdown formatting, and typo fixes. I reviewed the attached diff, PR description, and spec context; there is no approved spec context to compare against, and I found no blocking correctness or security concerns.

Concerns

  • No blocking concerns.
  • Non-blocking: a few touched lines still use legacy shortcut notation or quoted UI labels instead of the docs style guide format.

Verdict

Found: 0 critical, 0 important, 3 suggestions

Approve with nits

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

* **Or start the command yourself, then tag the agent in**
* Example:
* If you’ve already launched an interactive tool (for example `psql` or `npm run dev`), you can bring the agent into the running session using the "Use Agent" button in the terminal footer or via `CMD + I` .
* If you’ve already launched an interactive tool (for example `psql` or `npm run dev`), you can bring the agent into the running session using the "Use Agent" button in the terminal footer or via `CMD + I`.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 [SUGGESTION] This touched line still uses a quoted button label and legacy shortcut formatting; use bold UI text and Cmd+I per the docs style guide.

Suggested change
* If you’ve already launched an interactive tool (for example `psql` or `npm run dev`), you can bring the agent into the running session using the "Use Agent" button in the terminal footer or via `CMD + I`.
* If you’ve already launched an interactive tool (for example `psql` or `npm run dev`), you can bring the agent into the running session using the **Use Agent** button in the terminal footer or via `Cmd+I`.


:::tip
You can also open the Code Review panel with `CMDSHIFT+` on macOS or `CTRLSHIFT+` on Windows and Linux.
You can also open the Code Review panel with `CMD-SHIFT-+` on macOS or `CTRL-SHIFT-+` on Windows and Linux.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 [SUGGESTION] Use + separators and title-case modifier names for shortcuts, including the plus-key shortcut.

Suggested change
You can also open the Code Review panel with `CMD-SHIFT-+` on macOS or `CTRL-SHIFT-+` on Windows and Linux.
You can also open the Code Review panel with `Cmd+Shift++` on macOS or `Ctrl+Shift++` on Windows and Linux.

The main terminal window is not that different from other terminals - there's a place to type commands (Command Input) and a list of the previously executed commands and their outputs. Warp groups those together - each command and output create a Block. You can navigate blocks with your keyboard to easily check what was the command, learn whether it was successful or not, and what was the output, as well as more easily copy the command, output, or both for further processing.

A main entry point for discovering new features and actions is our Command Palette, which you can access by executing the cmd-p shortcut.
A main entry point for discovering new features and actions is our Command Palette, which you can access by executing the `CMD-P` shortcut.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 [SUGGESTION] Match the keyboard shortcut format used in the docs style guide.

Suggested change
A main entry point for discovering new features and actions is our Command Palette, which you can access by executing the `CMD-P` shortcut.
A main entry point for discovering new features and actions is our Command Palette, which you can access by pressing `Cmd+P`.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant