docs: drop teletype style for CompositePodGroup API kinds - #56912
docs: drop teletype style for CompositePodGroup API kinds#56912locker95 wants to merge 2 commits into
Conversation
👷 Deploy Preview for kubernetes-io-vnext-staging processing.
|
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Wrap remaining bare CompositePodGroup / CompositePodGroups mentions so they match the API resource naming guidance. Signed-off-by: Dean Chen <862469039@qq.com>
bf64ebe to
45094e0
Compare
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Style guide: API kinds are written verbatim, not in backticks. Leave field names, plugins, and condition codes in code style. Kubernetes-issue: 56893 Signed-off-by: Dean Chen <862469039@qq.com>
|
This is AI generated, I'm guessing. To err is human, but this pattern of mistakes reminds me of a computer. |
|
yeah fair — i used generative AI to help draft some of the wording. i still checked it against the style guide myself; first push had the backticks the wrong way around, sorry about that. fixed it in the follow-up commit so kinds are plain text, not teletype. |
Style guide says API kinds (CompositePodGroup, PodGroup, Workload, …) are written verbatim — no backticks. A bunch of the gang/PodGroup pages were wrapping those kind names in teletype.
Left field names (
CompositePodGroupTemplate), plugins, and condition codes alone.Targets
dev-1.37.Fixes #56893
This PR was written in part with the assistance of generative AI.