docs: use "true" and "false" consistently in the reference documentation#2330
Merged
tonyandrewmeyer merged 5 commits intocanonical:mainfrom Feb 19, 2026
Merged
Conversation
dimaqq
requested changes
Feb 17, 2026
james-garner-canonical
approved these changes
Feb 17, 2026
Contributor
james-garner-canonical
left a comment
There was a problem hiding this comment.
Changes look good and more consistent than we had previously. The updated contribution guidance is nice.
I think sometimes it's not clear whether 'true' or 'True' would fit better, but I think it's a nice improvement just eliminating 'True'.
Co-authored-by: James Garner <james.garner@canonical.com>
dimaqq
approved these changes
Feb 18, 2026
dimaqq
approved these changes
Feb 19, 2026
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
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.
Adjust the docstrings so that true and false are used consistently, and also adjust the style guide to explain our practice.
"true" and "false" mean "truth-y" and "false-y".
TrueandFalsemean the Python objects. We don't use "True" or "False" (unless the capitalisation is from the start of a sentence).Fixes #2291