docs: standardize OPAQUE brand capitalization#361
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
imran-siddique
added a commit
that referenced
this pull request
Jun 29, 2026
House style: no em dashes. Replaces all em dashes across docstrings, comments, markdown docs, and config: - prose (.md/.py/.sh): em dash -> colon - structured (.yaml/.yml/.toml): em dash -> comma (colon would change YAML meaning) - the one noqa directive kept valid (parenthesized note) - .json fixtures untouched; one Cedar comment -> comma; en-dash numeric ranges left as-is Rebased on main (after #361/#362). Verified: ruff + mypy clean, 756 unit tests pass.
imran-siddique
added a commit
that referenced
this pull request
Jun 29, 2026
House style: no em dashes. Replaces all em dashes across docstrings, comments, markdown docs, and config: - prose (.md/.py/.sh): em dash -> colon - structured (.yaml/.yml/.toml): em dash -> comma (colon would change YAML meaning) - the one noqa directive kept valid (parenthesized note) - .json fixtures untouched; one Cedar comment -> comma; en-dash numeric ranges left as-is Rebased on main (after #361/#362). Verified: ruff + mypy clean, 756 unit tests pass.
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
1 participant
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.
Standardizes the OPAQUE brand name to all-caps in human-facing prose across the docs (CHARTER, CHANGELOG, README, GOVERNANCE, SECURITY, LIMITATIONS, MAINTAINERS, and the spec/tutorials/testing pages). This is a casing-only change with no functional impact.
Code identifiers, provider keys (lowercase
opaque), the env varOPAQUE_ATTESTATION_URL, and all Python symbols were left untouched. Generic adjective uses of "opaque" were also left as-is.🤖 Generated with Claude Code