Mention CO and KO in Contracting Officer definition - #79
Merged
Conversation
Both acronyms already linked as aliases; spell them out in the popover copy so readers see either abbreviation maps to the same role.
jsolly
marked this pull request as ready for review
July 20, 2026 11:07
jsolly
enabled auto-merge (squash)
July 20, 2026 11:08
auto-merge was automatically disabled
July 20, 2026 11:09
Pull Request is not mergeable
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Yes — KO is especially common (notably in DoD usage), and CO is also widely used. Both were already glossary aliases for linking; the popover definition just didn’t say so.
Change
Contracting Officer definition now opens with: Also abbreviated CO or KO.
Linking for
CO/KO/COs/KOsis unchanged.