From 23f0efbf09b1487d7e2dc06b25a22cd68cdb6aef Mon Sep 17 00:00:00 2001 From: Ubuntu Date: Fri, 30 Jan 2026 19:22:32 +0000 Subject: [PATCH] docs: use straight quotes for code terms in installer guide --- docs/install/installer.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/install/installer.md b/docs/install/installer.md index f838735cf..6b371ce49 100644 --- a/docs/install/installer.md +++ b/docs/install/installer.md @@ -37,7 +37,7 @@ What it does (high level): - Choose install method: - `npm` (default): `npm install -g openclaw@latest` - `git`: clone/build a source checkout and install a wrapper script -- On Linux: avoid global npm permission errors by switching npm’s prefix to `~/.npm-global` when needed. +- On Linux: avoid global npm permission errors by switching npm's prefix to `~/.npm-global` when needed. - If upgrading an existing install: runs `openclaw doctor --non-interactive` (best effort). - For git installs: runs `openclaw doctor --non-interactive` after install/update (best effort). - Mitigates `sharp` native install gotchas by defaulting `SHARP_IGNORE_GLOBAL_LIBVIPS=1` (avoids building against system libvips). @@ -65,7 +65,7 @@ For `npm` installs, Git is *usually* not required, but some environments still e ### Why npm hits `EACCES` on fresh Linux -On some Linux setups (especially after installing Node via the system package manager or NodeSource), npm’s global prefix points at a root-owned location. Then `npm install -g ...` fails with `EACCES` / `mkdir` permission errors. +On some Linux setups (especially after installing Node via the system package manager or NodeSource), npm's global prefix points at a root-owned location. Then `npm install -g ...` fails with `EACCES` / `mkdir` permission errors. `install.sh` mitigates this by switching the prefix to: