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.
This commit is contained in:
Vincent Koc
2026-05-05 18:45:27 -07:00
parent 73d9044204
commit e36cb33379
4 changed files with 19 additions and 25 deletions

View File

@@ -7,10 +7,6 @@ read_when:
title: "GCP"
---
# OpenClaw on GCP Compute Engine (Docker, Production VPS Guide)
## Goal
Run a persistent OpenClaw Gateway on a GCP Compute Engine VM using Docker, with durable state, baked-in binaries, and safe restart behavior.
If you want "OpenClaw 24/7 for ~$5-12/mo", this is a reliable setup on Google Cloud.

View File

@@ -1,5 +1,5 @@
---
summary: "Install and configure Node.js for OpenClaw version requirements, install options, and PATH troubleshooting"
summary: "Install and configure Node.js for OpenClaw - version requirements, install options, and PATH troubleshooting"
title: "Node.js"
read_when:
- "You need to install Node.js before installing OpenClaw"
@@ -7,7 +7,7 @@ read_when:
- "npm install -g fails with permissions or PATH issues"
---
OpenClaw requires **Node 22.14 or newer**. **Node 24 is the default and recommended runtime** for installs, CI, and release workflows. Node 22 remains supported via the active LTS line. The [installer script](/install#alternative-install-methods) will detect and install Node automatically this page is for when you want to set up Node yourself and make sure everything is wired up correctly (versions, PATH, global installs).
OpenClaw requires **Node 22.14 or newer**. **Node 24 is the default and recommended runtime** for installs, CI, and release workflows. Node 22 remains supported via the active LTS line. The [installer script](/install#alternative-install-methods) will detect and install Node automatically - this page is for when you want to set up Node yourself and make sure everything is wired up correctly (versions, PATH, global installs).
## Check your version
@@ -68,9 +68,9 @@ If this prints `v24.x.x` or higher, you're on the recommended default. If it pri
<Accordion title="Using a version manager (nvm, fnm, mise, asdf)">
Version managers let you switch between Node versions easily. Popular options:
- [**fnm**](https://github.com/Schniz/fnm) fast, cross-platform
- [**nvm**](https://github.com/nvm-sh/nvm) widely used on macOS/Linux
- [**mise**](https://mise.jdx.dev/) polyglot (Node, Python, Ruby, etc.)
- [**fnm**](https://github.com/Schniz/fnm) - fast, cross-platform
- [**nvm**](https://github.com/nvm-sh/nvm) - widely used on macOS/Linux
- [**mise**](https://mise.jdx.dev/) - polyglot (Node, Python, Ruby, etc.)
Example with fnm:
@@ -137,6 +137,6 @@ Add the `export PATH=...` line to your `~/.bashrc` or `~/.zshrc` to make it perm
## Related
- [Install Overview](/install) all installation methods
- [Updating](/install/updating) keeping OpenClaw up to date
- [Getting Started](/start/getting-started) first steps after install
- [Install Overview](/install) - all installation methods
- [Updating](/install/updating) - keeping OpenClaw up to date
- [Getting Started](/start/getting-started) - first steps after install

View File

@@ -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 antibot 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`, orangetinted 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:

View File

@@ -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 (110).
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