docs: typography hygiene across 6 pages

Replaced 74 typography characters (curly quotes, apostrophes, em/en
dashes, non-breaking hyphens) with ASCII equivalents per
docs/CLAUDE.md heading and content hygiene rules.

- docs/gateway/opentelemetry.md: 13 chars
- docs/channels/msteams.md: 13 chars
- docs/tools/skills.md: 12 chars
- docs/start/setup.md: 12 chars
- docs/nodes/location-command.md: 12 chars
- docs/concepts/context-engine.md: 12 chars

docs/tools/skills.md

@@ -80,7 +80,7 @@ allowlists decide which skills an agent can actually use.
     - Omit `agents.list[].skills` to inherit `agents.defaults.skills`.
     - Set `agents.list[].skills: []` for no skills.
     - A non-empty `agents.list[].skills` list is the **final** set for that
-      agent — it does not merge with defaults.
+      agent - it does not merge with defaults.
     - The effective allowlist applies across prompt building, skill
       slash-command discovery, sandbox sync, and skill snapshots.
   </Accordion>
@@ -92,7 +92,7 @@ Plugins can ship their own skills by listing `skills` directories in
 `openclaw.plugin.json` (paths relative to the plugin root). Plugin skills
 load when the plugin is enabled. This is the right place for tool-specific
 operating guides that are too long for the tool description but should be
-available whenever the plugin is installed — for example, the browser
+available whenever the plugin is installed - for example, the browser
 plugin ships a `browser-automation` skill for multi-step browser control.
 
 Plugin skill directories are merged into the same low-precedence path as
@@ -158,7 +158,7 @@ Prefer sandboxed runs for untrusted inputs and risky tools. See
 
 - Workspace and extra-dir skill discovery only accepts skill roots and `SKILL.md` files whose resolved realpath stays inside the configured root.
 - Gateway-backed skill dependency installs (`skills.install`, onboarding, and the Skills settings UI) run the built-in dangerous-code scanner before executing installer metadata. `critical` findings block by default unless the caller explicitly sets the dangerous override; suspicious findings still warn only.
-- `openclaw skills install <slug>` is different — it downloads a ClawHub skill folder into the workspace and does not use the installer-metadata path above.
+- `openclaw skills install <slug>` is different - it downloads a ClawHub skill folder into the workspace and does not use the installer-metadata path above.
 - `skills.entries.*.env` and `skills.entries.*.apiKey` inject secrets into the **host** process for that agent turn (not the sandbox). Keep secrets out of prompts and logs.
 
 For a broader threat model and checklists, see [Security](/gateway/security).
@@ -302,7 +302,7 @@ metadata:
     - If multiple installers are listed, the gateway picks a single preferred option (brew when available, otherwise node).
     - If all installers are `download`, OpenClaw lists each entry so you can see the available artifacts.
     - Installer specs can include `os: ["darwin"|"linux"|"win32"]` to filter options by platform.
-    - Node installs honor `skills.install.nodeManager` in `openclaw.json` (default: npm; options: npm/pnpm/yarn/bun). This only affects skill installs; the Gateway runtime should still be Node — Bun is not recommended for WhatsApp/Telegram.
+    - Node installs honor `skills.install.nodeManager` in `openclaw.json` (default: npm; options: npm/pnpm/yarn/bun). This only affects skill installs; the Gateway runtime should still be Node - Bun is not recommended for WhatsApp/Telegram.
     - Gateway-backed installer selection is preference-driven: when install specs mix kinds, OpenClaw prefers Homebrew when `skills.install.preferBrew` is enabled and `brew` exists, then `uv`, then the configured node manager, then other fallbacks like `go` or `download`.
     - If every install spec is `download`, OpenClaw surfaces all download options instead of collapsing to one preferred installer.
 
@@ -362,7 +362,7 @@ under `skills.entries` in `~/.openclaw/openclaw.json`:
 </ParamField>
 
 If the skill name contains hyphens, quote the key (JSON5 allows quoted
-keys). Config keys match the **skill name** by default — if a skill
+keys). Config keys match the **skill name** by default - if a skill
 defines `metadata.openclaw.skillKey`, use that key under `skills.entries`.
 
 <Note>
@@ -464,7 +464,7 @@ skill plus your actual field lengths.
 
 OpenClaw ships a baseline set of skills as **bundled skills** with the
 install (npm package or OpenClaw.app). `~/.openclaw/skills` exists for
-local overrides — for example, pinning or patching a skill without
+local overrides - for example, pinning or patching a skill without
 changing the bundled copy. Workspace skills are user-owned and override
 both on name conflicts.
 
@@ -475,9 +475,9 @@ schema: [Skills config](/tools/skills-config).
 
 ## Related
 
-- [ClawHub](/tools/clawhub) — public skills registry
-- [Creating skills](/tools/creating-skills) — building custom skills
-- [Plugins](/tools/plugin) — plugin system overview
-- [Skill Workshop plugin](/plugins/skill-workshop) — generate skills from agent work
-- [Skills config](/tools/skills-config) — skill configuration reference
-- [Slash commands](/tools/slash-commands) — all available slash commands
+- [ClawHub](/tools/clawhub) - public skills registry
+- [Creating skills](/tools/creating-skills) - building custom skills
+- [Plugins](/tools/plugin) - plugin system overview
+- [Skill Workshop plugin](/plugins/skill-workshop) - generate skills from agent work
+- [Skills config](/tools/skills-config) - skill configuration reference
+- [Slash commands](/tools/slash-commands) - all available slash commands