docs: fix terminal docs factual issues + keybinding/link style pass, reconcile with main, settle key-chord casing (GROW-6086)

src/content/docs/agents/capabilities/agent-profiles-permissions.mdx

@@ -121,17 +121,17 @@ To learn how to build and configure your own MCP server, check out the [MCP feat
 
 ## Run until completion
 
-During an Agent interaction, you can give the Agent full autonomy for the current task. When auto-approve is on, every suggested command runs immediately until the task finishes, or you stop it with `Ctrl + C`.
+During an Agent interaction, you can give the Agent full autonomy for the current task. When auto-approve is on, every suggested command runs immediately until the task finishes, or you stop it with `Ctrl+C`.
 
 <Tabs>
   <TabItem label="macOS">
-    Auto-approve all Agent actions with: `CMD + SHIFT + I`
+    Auto-approve all Agent actions with: `⌘+Shift+I`
   </TabItem>
   <TabItem label="Windows">
-    Auto-approve all Agent actions with: `CTRL + SHIFT + I`
+    Auto-approve all Agent actions with: `Ctrl+Shift+I`
   </TabItem>
   <TabItem label="Linux">
-    Auto-approve all Agent actions with: `CTRL + SHIFT + I`
+    Auto-approve all Agent actions with: `Ctrl+Shift+I`
   </TabItem>
 </Tabs>
 

src/content/docs/agents/capabilities/full-terminal-use.mdx

@@ -112,22 +112,22 @@ The behavior differs based on where you start the long-running command:
 <Tabs>
   <TabItem label="From terminal view">
     1. Run an interactive command (e.g., `python`, `psql`)
-    2. Press `⌘↩` (macOS) or `Ctrl+Shift+Enter` (Windows/Linux), or use `⌘I` (macOS) / `Ctrl+I` (Windows/Linux), to tag in the agent
+    2. Press `⌘+Enter` (macOS) or `Ctrl+Shift+Enter` (Windows/Linux), or use `⌘+I` (macOS) / `Ctrl+I` (Windows/Linux), to tag in the agent
     3. The input switches to Agent Mode with full controls
     4. When you exit, an agent conversation block appears in your terminal block list
     5. Click the block to reopen the full conversation with your LRC interaction context
   </TabItem>
   <TabItem label="From agent view">
     1. The agent runs an interactive command as part of your conversation
-    2. Use `⌘↩` (macOS) or `Ctrl+Shift+Enter` (Windows/Linux) to tag in if the agent isn't already interacting
+    2. Use `⌘+Enter` (macOS) or `Ctrl+Shift+Enter` (Windows/Linux) to tag in if the agent isn't already interacting
     3. The UI stays the same since you're already in agent view
     4. When you exit, the interaction remains part of your conversation. No separate block is created in the terminal block list
     5. Commands run in agent view are automatically included as context
   </TabItem>
 </Tabs>
 
 :::note
-You can also use `CMD + I` (macOS) or `CTRL + I` (Windows/Linux) to toggle agent control in either view.
+You can also use `⌘+I` (macOS) or `Ctrl+I` (Windows/Linux) to toggle agent control in either view.
 :::
 
 #### Showing and hiding agent responses
@@ -136,7 +136,7 @@ Warp gives you control over how much agent output appears in Full Terminal Use.
 
 **Toggle visibility**
 
-Use the `Hide responses` or `Show responses` button or `CMD + G` in the interactive command footer to switch between showing all agent output or hiding it from the terminal view.
+Use the `Hide responses` or `Show responses` button or `⌘+G` in the interactive command footer to switch between showing all agent output or hiding it from the terminal view.
 
 Note that this only affects the agent's messages and proposals; your terminal state and command output remain unchanged.
 
@@ -157,10 +157,10 @@ You control how much autonomy the agent has when interacting with the terminal.
 
 Each time the agent wants to take an action inside an interactive shell, you’ll see the agent’s reasoning, a brief explanation, and the proposed command. From there you can:
 
-* Allow the command once (for example by approving it or pressing `ENTER`).
-* Turn on auto-approval for similar commands in this session (for example with `CMD + SHIFT + I`).
-* Refine the request with `CTRL + C`, which clears the proposed action and lets you follow up with a different query.
-* Take over manually with `CMD + I`, which stops the agent from issuing any further PTY writes until you hand control back.
+* Allow the command once (for example by approving it or pressing `Enter`).
+* Turn on auto-approval for similar commands in this session (for example with `⌘+Shift+I`).
+* Refine the request with `Ctrl+C`, which clears the proposed action and lets you follow up with a different query.
+* Take over manually with `⌘+I`, which stops the agent from issuing any further PTY writes until you hand control back.
 
 <figure>
 ![Allow, Refine, or Take over an agent response.](../../../../assets/agent-platform/allow-refine-takeover.png)

src/content/docs/agents/local-agents/active-ai.mdx

@@ -21,7 +21,7 @@ To disable, go to **Settings** > **Agents** > **Warp Agent** > **Active AI** > *
 
 #### Accepting a prompt suggestion
 
-If you press `CTRL-ENTER` (on macOS), `ALT-SHIFT-ENTER` (on Linux/Windows), or click on the chip, the suggestion will auto-populate into your input and run against [Agent Mode](/agents/local-agents/interacting-with-agents/) (with the most recent block attached).
+If you press `Ctrl+Enter` (on macOS), `Alt+Shift+Enter` (on Linux/Windows), or click on the chip, the suggestion will auto-populate into your input and run against [Agent Mode](/agents/local-agents/interacting-with-agents/) (with the most recent block attached).
 
 :::note
 Prompt Suggestions use an LLM to generate prompts based on your terminal session, specifically the most recent block. These AI requests do not contribute towards your AI limits. However, any accepted prompts run in Agent Mode contribute as normal. To turn it off, go to **Settings** > **Agents** > **Warp Agent** > **Active AI**.
@@ -47,7 +47,7 @@ Next Command is an LLM-based feature that uses your command history (enriched wi
 
 #### Accepting Next Command suggestions
 
-Press `→` or `CTRL-F` to accept a Next Command suggestion into your input buffer, then press `ENTER` to execute it. You can change the accept keybinding (for example, to `TAB`) via the inline keybinding picker that appears next to the suggestion.
+Press `→` or `Ctrl+F` to accept a Next Command suggestion into your input buffer, then press `Enter` to execute it. You can change the accept keybinding (for example, to `Tab`) via the inline keybinding picker that appears next to the suggestion.
 
 #### Billing
 
@@ -59,15 +59,15 @@ Suggested Code Diffs automatically surface potential fixes for command-line erro
 
 !["Generating fix" banner shown after a command-line error while Warp prepares a proposed diff.](../../../../assets/agent-platform/suggested-code-diffs-generating-fix.png)
 
-When an error occurs, Warp evaluates whether it is appropriate for an LLM to generate a fix. If so, a “Generating fix” banner will appear while Warp prepares a proposed diff. You can stop this process at any time by pressing `CTRL + C` or the stop button.
+When an error occurs, Warp evaluates whether it is appropriate for an LLM to generate a fix. If so, a “Generating fix” banner will appear while Warp prepares a proposed diff. You can stop this process at any time by pressing `Ctrl+C` or the stop button.
 
 ![Suggested code diff with options to dismiss or accept the proposed fix.](../../../../assets/agent-platform/suggested-code-diffs.png)
 
 #### Using a suggested code diff
 
-Once the diff is generated, you can either dismiss it or accept it. Acceptance can be done directly via the buttons in the diff view, or with `CMD + ENTER` on macOS and `CTRL + ENTER` on Windows/Linux.
+Once the diff is generated, you can either dismiss it or accept it. Acceptance can be done directly via the buttons in the diff view, or with `⌘+Enter` on macOS and `Ctrl+Enter` on Windows/Linux.
 
-You can also view additional details of the diff by pressing `CMD + E` (macOS) or `CTRL + E` (Windows/Linux), which expands the view to allow further inspection (including refining or editing it). You can also use `↓` to view the entire diff.
+You can also view additional details of the diff by pressing `⌘+E` (macOS) or `Ctrl+E` (Windows/Linux), which expands the view to allow further inspection (including refining or editing it). You can also use `↓` to view the entire diff.
 
 **Billing**
 

src/content/docs/agents/local-agents/agent-context/blocks-as-context.mdx

@@ -27,46 +27,46 @@ The most common use case is to ask the AI to fix an error. You can attach the er
   <TabItem label="macOS">
     **Attach a previous block**
 
-    * To attach blocks to a query, you can use `CMD-UP` to attach the previous block as context to the query. While holding `CMD`, you can then use your `UP/DOWN` keys to pick another block to attach.
-      * You can also use your mouse to attach blocks in your session. Hold `CMD` as you click on other blocks to extend your block selection.
+    * To attach blocks to a query, you can use `⌘+↑` to attach the previous block as context to the query. While holding `⌘`, you can then use your `↑/↓` keys to pick another block to attach.
+      * You can also use your mouse to attach blocks in your session. Hold `⌘` as you click on other blocks to extend your block selection.
 
     **Clear a previous block**
 
-    * To clear blocks from a query, you can use `CMD-DOWN` until the blocks are removed from context.
-      * You can also use your mouse to clear blocks in your session. Hold `CMD` as you click on an attached block to clear it.
+    * To clear blocks from a query, you can use `⌘+↓` until the blocks are removed from context.
+      * You can also use your mouse to clear blocks in your session. Hold `⌘` as you click on an attached block to clear it.
 
     :::note
-    When using "Pin to the top" [Input Position](/terminal/appearance/input-position/), the direction for attaching or detaching is reversed (i.e. `CMD-DOWN` attaches blocks to context, while `CMD-UP` clears blocks from context).
+    When using "Pin to the top" [Input Position](/terminal/appearance/input-position/), the direction for attaching or detaching is reversed (i.e. `⌘+↓` attaches blocks to context, while `⌘+↑` clears blocks from context).
     :::
   </TabItem>
   <TabItem label="Windows">
     **Attach a previous block**
 
-    * To attach blocks to a query, you can use `CTRL-UP` to attach the previous block as context to the query. While holding `CTRL`, you can then use your `UP/DOWN` keys to pick another block to attach.
-      * You can also use your mouse to select blocks in your session. Hold `CTRL` as you click on other blocks to extend your block selection.
+    * To attach blocks to a query, you can use `Ctrl+↑` to attach the previous block as context to the query. While holding `Ctrl`, you can then use your `↑/↓` keys to pick another block to attach.
+      * You can also use your mouse to select blocks in your session. Hold `Ctrl` as you click on other blocks to extend your block selection.
 
     **Clear a previous block**
 
-    * To clear blocks from a query, you can use `CTRL-DOWN` until the blocks are removed from context.
-      * You can also use your mouse to clear blocks in your session. Hold `CTRL` as you click on an attached block to clear it.
+    * To clear blocks from a query, you can use `Ctrl+↓` until the blocks are removed from context.
+      * You can also use your mouse to clear blocks in your session. Hold `Ctrl` as you click on an attached block to clear it.
 
     :::note
-    When using "Pin to the top" [Input Position](/terminal/appearance/input-position/), the direction for attaching or detaching is reversed (i.e. `CTRL-DOWN` attaches blocks to context, while `CTRL-UP` clears blocks from context).
+    When using "Pin to the top" [Input Position](/terminal/appearance/input-position/), the direction for attaching or detaching is reversed (i.e. `Ctrl+↓` attaches blocks to context, while `Ctrl+↑` clears blocks from context).
     :::
   </TabItem>
   <TabItem label="Linux">
     **Attach a previous block**
 
-    * To attach blocks to a query, you can use `CTRL-UP` to attach the previous block as context to the query. While holding `CTRL`, you can then use your `UP/DOWN` keys to pick another block to attach.
-      * You can also use your mouse to select blocks in your session. Hold `CTRL` as you click on other blocks to extend your block selection.
+    * To attach blocks to a query, you can use `Ctrl+↑` to attach the previous block as context to the query. While holding `Ctrl`, you can then use your `↑/↓` keys to pick another block to attach.
+      * You can also use your mouse to select blocks in your session. Hold `Ctrl` as you click on other blocks to extend your block selection.
 
     **Clear a previous block**
 
-    * To clear blocks from a query, you can use `CTRL-DOWN` until the blocks are removed from context.
-      * You can also use your mouse to clear blocks in your session. Hold `CTRL` as you click on an attached block to clear it.
+    * To clear blocks from a query, you can use `Ctrl+↓` until the blocks are removed from context.
+      * You can also use your mouse to clear blocks in your session. Hold `Ctrl` as you click on an attached block to clear it.
 
     :::note
-    When using "Pin to the top" [Input Position](/terminal/appearance/input-position/), the direction for attaching or detaching is reversed (i.e. `CTRL-DOWN` attaches blocks to context, while `CTRL-UP` clears blocks from context).
+    When using "Pin to the top" [Input Position](/terminal/appearance/input-position/), the direction for attaching or detaching is reversed (i.e. `Ctrl+↓` attaches blocks to context, while `Ctrl+↑` clears blocks from context).
     :::
   </TabItem>
 </Tabs>
@@ -101,5 +101,5 @@ You can also manually attach terminal view blocks to add additional context from
 
 When you select blocks in terminal view and start a new conversation, those blocks become **pending context**:
 
-* **Pending context** - Blocks are selected but the conversation hasn't started yet. If you deselect the blocks (`ESC` or `CMD-K` on macOS, `ESC` or `CTRL-K` on Windows/Linux), they're removed from the agent view.
+* **Pending context** - Blocks are selected but the conversation hasn't started yet. If you deselect the blocks (`Esc` or `⌘+K` on macOS, `Esc` or `Ctrl+K` on Windows/Linux), they're removed from the agent view.
 * **Attached context** - Once you submit your first query, the pending blocks become attached to the conversation and remain part of the context.

src/content/docs/agents/local-agents/agent-context/selection-as-context.mdx

@@ -12,7 +12,7 @@ Attach text selections or diff hunks directly from Warp's code editor or Code Re
 When you have Warp’s [native code editor](/code/code-editor/) open beside a regular pane, you can easily attach specific lines of code as context:
 
 1. **Select text** in the editor. A tooltip will appear in the bottom-right corner of the selection.
-2. **Add as context** by clicking the tooltip or using the keyboard shortcuts `Cmd + L` (macOS) or `CTRL + SHIFT + L` (Windows or Linux).
+2. **Add as context** by clicking the tooltip or using the keyboard shortcuts `⌘+L` (macOS) or `Ctrl+Shift+L` (Windows or Linux).
 3. Warp automatically adds the relative file path and context, in addition to the line numbers of the hunk, as a formatted string into the prompt.
 
 This makes it easy to highlight just the lines you want the Agent to analyze or modify.
@@ -40,6 +40,6 @@ This helps the Agent understand exactly what has been modified, making it easier
 
 You can select code, files, or snippets and feed them directly to a running third-party CLI agent session without copy-pasting or switching tools.
 
-When a third-party agent (Claude Code, Codex, OpenCode, etc.) is running in a Warp tab, select text in Warp's code editor or Code Review panel and attach it as context to that agent's session using `Cmd + L` (macOS) or `CTRL + SHIFT + L` (Windows/Linux). This works the same way as attaching context to Warp's built-in Agent.
+When a third-party agent (Claude Code, Codex, OpenCode, etc.) is running in a Warp tab, select text in Warp's code editor or Code Review panel and attach it as context to that agent's session using `⌘+L` (macOS) or `Ctrl+Shift+L` (Windows/Linux). This works the same way as attaching context to Warp's built-in Agent.
 
 For more on third-party agent support, see [Third-party CLI agents](/agents/cli-agents/overview/).

src/content/docs/agents/local-agents/code-diffs.mdx

@@ -35,9 +35,9 @@ You can also choose whether Warp automatically opens the [Code Review](/code/cod
 
 When an Agent generates a code diff, Warp opens it in a built-in text editor with a visual diff view. Changes are grouped into clear hunks for easy inspection.
 
-* Use the `UP` and `DOWN` arrow keys (or mouse clicks) to move between hunks.
-* For multi-file changes, use `LEFT` and `RIGHT` arrow keys to switch between files.
-* Once satisfied with the changes, you can apply the diffs using `ENTER` or clicking "**Accept Changes**" to apply the modifications.
+* Use the `↑` and `↓` arrow keys (or mouse clicks) to move between hunks.
+* For multi-file changes, use `←` and `→` arrow keys to switch between files.
+* Once satisfied with the changes, you can apply the diffs using `Enter` or clicking "**Accept Changes**" to apply the modifications.
 
 :::caution
 These modifications will not be applied to the files unless you explicitly accept them.
@@ -49,7 +49,7 @@ If the initial suggestion needs more work:
 
 * Press `R` or select the "**Refine**" button to provide follow-up instructions in natural language. The agent will regenerate the diff based on your input.
 * To manually adjust the code, press `E` or click "**Edit**" to switch into an editable view.
-* To cancel a pending operation, use `CTRL-C` (on macOS, Windows, or Linux). Similarly, you can exit the editor at any time with `ESC`.
+* To cancel a pending operation, use `Ctrl+C` (on macOS, Windows, or Linux). Similarly, you can exit the editor at any time with `Esc`.
 
 :::note
 You can open up code files in Warp in various different ways, refer to: [Opening files in Warp](/code/code-editor/#opening-files-in-warp)