fix(onboarding): different identity = separate proxy instance

RHCLOUD-48703

Author: Hyperkid123

docs/onboarding-new-instance.md

@@ -525,7 +525,7 @@ When changes span multiple repos, merge in this order:
 ### Shared identities
 All bot instances share credentials from `devbot-secrets` — Jira, GitHub, GitLab, GPG, and GCP. This means all instances push code, open PRs, and comment on Jira as the same user. The bot identifies its own Jira comments by content patterns (structured reports, PR links, tables), not by username.
 
-Each instance needs its own Jira credentials and proxy container (see **Vault Secrets** in Step 4). The same applies to GitHub/GitLab identities — if your instance needs to push as a different user, you'll need separate PATs in your Vault secret.
+A different identity (Jira, GitHub, or GitLab) requires a separate proxy instance — credentials are baked into the proxy container, not the bot pod. See **Shared vs Per-Instance Proxy** in Step 2 and **Vault Secrets** in Step 4.
 
 ### `BOT_BOARD_NAME` is fragile
 If someone renames the Jira board, `claim-ticket` breaks. Consider using `BOT_BOARD_ID` (stable numeric ID) instead. The ticket query (`new-work`) doesn't use the board at all — it's label-only with `sprint in openSprints()`.