docs: drop in-body H1s and typography hygiene across 4 pages

docs/install/gcp.md: removed the duplicate '# OpenClaw on GCP Compute
Engine (Docker, Production VPS Guide)' H1 plus its redundant '## Goal'
header. Mintlify renders the title from frontmatter, so the body H1
created a brittle anchor and the prose now starts directly with the
goal sentence.

docs/install/node.md: replaced 8 typography characters (curly quotes
and non-breaking hyphens) with ASCII equivalents.

docs/tools/duckduckgo-search.md: replaced 9 typography characters with
ASCII equivalents.

docs/tools/browser-login.md: removed the duplicate '# Browser login +
X/Twitter posting' H1 (Mintlify renders title from frontmatter; the
'+' would also have produced a brittle anchor). Replaced 2 typography
characters with ASCII equivalents.

docs/tools/browser-login.md

@@ -6,19 +6,17 @@ read_when:
 title: "Browser login"
 ---
 
-# Browser login + X/Twitter posting
-
 ## Manual login (recommended)
 
 When a site requires login, **sign in manually** in the **host** browser profile (the openclaw browser).
 
-Do **not** give the model your credentials. Automated logins often trigger anti‑bot defenses and can lock the account.
+Do **not** give the model your credentials. Automated logins often trigger anti-bot defenses and can lock the account.
 
 Back to the main browser docs: [Browser](/tools/browser).
 
 ## Which Chrome profile is used?
 
-OpenClaw controls a **dedicated Chrome profile** (named `openclaw`, orange‑tinted UI). This is separate from your daily browser profile.
+OpenClaw controls a **dedicated Chrome profile** (named `openclaw`, orange-tinted UI). This is separate from your daily browser profile.
 
 For agent browser tool calls:
 

docs/tools/duckduckgo-search.md

@@ -12,13 +12,13 @@ key or account is required.
 
 <Warning>
   DuckDuckGo is an **experimental, unofficial** integration that pulls results
-  from DuckDuckGo's non-JavaScript search pages — not an official API. Expect
+  from DuckDuckGo's non-JavaScript search pages - not an official API. Expect
   occasional breakage from bot-challenge pages or HTML changes.
 </Warning>
 
 ## Setup
 
-No API key needed — just set DuckDuckGo as your provider:
+No API key needed - just set DuckDuckGo as your provider:
 
 <Steps>
   <Step title="Configure">
@@ -69,7 +69,7 @@ Search query.
 </ParamField>
 
 <ParamField path="count" type="number" default="5">
-Results to return (1–10).
+Results to return (1-10).
 </ParamField>
 
 <ParamField path="region" type="string">
@@ -80,19 +80,19 @@ DuckDuckGo region code (e.g. `us-en`, `uk-en`, `de-de`).
 SafeSearch level.
 </ParamField>
 
-Region and SafeSearch can also be set in plugin config (see above) — tool
+Region and SafeSearch can also be set in plugin config (see above) - tool
 parameters override config values per-query.
 
 ## Notes
 
-- **No API key** — works out of the box, zero configuration
-- **Experimental** — gathers results from DuckDuckGo's non-JavaScript HTML
+- **No API key** - works out of the box, zero configuration
+- **Experimental** - gathers results from DuckDuckGo's non-JavaScript HTML
   search pages, not an official API or SDK
-- **Bot-challenge risk** — DuckDuckGo may serve CAPTCHAs or block requests
+- **Bot-challenge risk** - DuckDuckGo may serve CAPTCHAs or block requests
   under heavy or automated use
-- **HTML parsing** — results depend on page structure, which can change without
+- **HTML parsing** - results depend on page structure, which can change without
   notice
-- **Auto-detection order** — DuckDuckGo is the first key-free fallback
+- **Auto-detection order** - DuckDuckGo is the first key-free fallback
   (order 100) in auto-detection. API-backed providers with configured keys run
   first, then Ollama Web Search (order 110), then SearXNG (order 200)
 - **SafeSearch defaults to moderate** when not configured