docs(quickstart): keep sandbox name examples consistent

[WilliamK112]

Summary

Keeps the OpenClaw quickstart sandbox name consistent by using my-gpt-claw in the terminal chat example, matching the review summary and install output shown earlier on the page.

Related Issue

Addresses #5631 item 2.

Changes

• Adds a short note that my-gpt-claw is the example sandbox name and should be replaced with the user's own onboarding sandbox name.
• Updates the terminal connect example from my-assistant to my-gpt-claw.

Type of Change

• Code change for a new feature, bug fix, or refactor.
• Code change with doc updates.
• Doc only. Prose changes without code sample modifications.
• Doc only. Includes code sample changes.

Testing

• npx prek run --all-files passes (or equivalently make check).
• npm test passes.
• make docs builds without warnings. (for doc-only changes)

Targeted docs check run:

• npm run docs completed with 0 errors and 2 existing Fern warnings reported without details by default.

Checklist

General

• I have read and followed the contributing guide.
• I have read and followed the style guide. (for doc-only changes)

Doc Changes

• Follows the style guide.
• Cross-references and links verified by npm run docs.

Signed-off-by: WilliamK112 164879897+WilliamK112@users.noreply.github.com

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[wscurran]

✨ Thanks for the proposed fix addressing the sandbox name inconsistency in the quickstart guide. This proposes a way to align the terminal connect example with the review summary and install output by using my-gpt-claw throughout.

---

Related open issues:

• #5631 [All Platforms][Docs] docs/get-started/quickstart.mdx — non-interactive onboard example missing required env vars; sandbox name inconsistency

[miyoungc]

Thanks for the docs fix. Before this can land, please work through the GitHub Verified commit requirement for the commit on this PR. The contributor guides cover this requirement as well, so please use those steps to make sure the PR history shows properly verified commits.

Since force-push is not allowed, you'd need to create a new PR.

[WilliamK112]

Closing in favor of #5723, which contains the same docs-only fix rebuilt on GitHub Verified signed commits as requested.