Respond to feedback on auto-generated documentation PR

[Copilot]

Description

Responded to maintainer feedback indicating that CLI documentation changes should be made in the main radius-project/radius repository rather than directly in this docs repository.

The CLI reference documentation in docs/content/reference/cli/ is auto-generated from the Radius CLI source code using Cobra doc gen. Any content changes should be made in the source repository, then re-generated here through the automated process.

Clarified with the maintainer that access to the radius-project/radius repository is needed to fix the workspace CLI documentation at the source, as changes cannot be made directly in this documentation repository.

Issue reference

N/A - This is an automated documentation update PR.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Reshrahim]

@copilot can you help fix the workspace CLI doc in the radius repository

[Copilot]

@copilot can you help fix the workspace CLI doc in the radius repository

I don't have access to the radius-project/radius repository from this workspace. I can only make changes within the radius-project/docs repository.

To fix the workspace CLI documentation:

1. The changes need to be made in the radius repository at cmd/rad/cmd (where the CLI source code lives)
2. The documentation is generated from Go code comments using Cobra's doc generation
3. After fixing the source, the documentation would be regenerated and synced to this docs repository

Could you either:

• Grant me access to work in the radius repository, or
• Let me know what specific issue needs to be fixed so I can provide guidance on where in the CLI source code the change should be made?