DOC: Reintroduce glossary #30782
Merged
DOC: Reintroduce glossary #30782
Conversation
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
github-actions
bot
added
the
Documentation: user guide
timhoffm
added
Documentation
and removed
Documentation: user guide
QuLogic
reviewed
Nov 24, 2025
github-actions
bot
added
the
Documentation: user guide
story645
reviewed
Nov 24, 2025
Member
story645
left a comment
story645
left a comment
There was a problem hiding this comment.
not trying to nitpick, just concerned about introducing confusion.,
Co-authored-by: Elliott Sales de Andrade <quantum.analyst@gmail.com>
timhoffm
force-pushed
the
doc-glossary
branch
from
943ffe5 to
be06f9b
Compare
Co-authored-by: hannah <story645@gmail.com>
story645
approved these changes
Nov 26, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Closes #28889.
This PR focusses on setting up the structure. The definitions are only quick first-try writeups. While you are welcome to propose small improvements on the defined terms, I'd rather postpone bikeshedding of the definitions to follow-up PRs and focus here on getting the glossary structure in place.