Docs: improve clarity and security guidance for SSH keys in CI/CD
What does this MR do and why?
This merge request improves clarity, consistency, and security guidance in the SSH keys with GitLab CI/CD documentation.
The goal is to make best practices around SSH key usage in CI/CD pipelines easier to understand and harder to misuse, without changing any product behavior.
References
- Related issue: #587532 (closed)
- GitLab documentation guidelines:
https://handbook.gitlab.com/handbook/product/ux/technical-writing/
Screenshots or screen recordings
Not applicable — documentation-only change (no UI impact).
How to set up and validate locally
- Review the updated documentation content for clarity and consistency.
- Confirm that no functional or behavioral changes are introduced.
- Ensure wording aligns with existing GitLab CI/CD security guidance.
MR acceptance checklist
- This MR is scoped to documentation only
- No product behavior or logic is changed
- Security guidance is clarified without introducing new risks
- Documentation follows GitLab technical writing standards