docs: address review feedback

Author: clean6378-max-it

.github/CODEOWNERS

@@ -2,17 +2,9 @@
 # Last match wins; see https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners
 #
 # Review owners (development + code review): @clean6378-max-it (Chen), @timon0305 (Zilin)
+# Both are write collaborators on this repo.
 #
 # Final approval, merge sequencing, and no-self-merge rules are enforced by branch
 # protection / automation, not by listing additional owners here.
 
-# Default owners for the repository.
 *                       @clean6378-max-it @timon0305
-
-# Docs and contributor process
-/docs/                  @clean6378-max-it @timon0305
-/CONTRIBUTING.md        @clean6378-max-it @timon0305
-/README.md              @clean6378-max-it @timon0305
-
-# CI and workflow changes
-/.github/               @clean6378-max-it @timon0305

README.md

@@ -145,8 +145,6 @@ claude-code-chat-browser/
 
 See **[`CONTRIBUTING.md`](CONTRIBUTING.md)** for full setup, conventions, and where to change each layer. New contributors should follow **[`docs/onboarding.md`](docs/onboarding.md)** for a first-PR walkthrough and reading order.
 
-**Maintainer coverage:** commit activity is currently concentrated on a small set of identities (bus-factor risk). Mitigations: [`.github/CODEOWNERS`](.github/CODEOWNERS) routes code review to @clean6378-max-it and @timon0305; final merge approval (@wpak-ai) is enforced via branch protection, plus [`docs/onboarding.md`](docs/onboarding.md) for contributor ramp-up.
-
 Quick start:
 
 ```bash

docs/onboarding.md

@@ -25,15 +25,13 @@ For API or export changes, also skim [`api/error_codes.py`](../api/error_codes.p
 
 ### 1. Fork and clone
 
-```powershell
+```bash
 # GitHub UI: fork cppalliance/claude-code-chat-browser to your account, then:
 git clone https://github.com/<your-user>/claude-code-chat-browser.git
 cd claude-code-chat-browser
 git remote add upstream https://github.com/cppalliance/claude-code-chat-browser.git
 ```
 
-On macOS/Linux, use the same `git clone` / `git remote add` commands in your shell.
-
 ### 2. Create a branch
 
 Branch names follow `feat/<topic>`, `fix/<topic>`, `docs/<topic>`, etc. (see [CONTRIBUTING.md](../CONTRIBUTING.md#branching-and-pull-requests)).