docs: fix missing preposition in schema page#564
Merged
Conversation
Signed-off-by: Amin8r <mohammadamin0831.ma@gmail.com>
Contributor
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
Contributor
|
Preview deployment skipped — @Amin8r does not have write access to this repository. A maintainer can trigger a preview deployment by re-running this workflow. |
Contributor
Author
|
I have read the CLA Document and I hereby sign the CLA |
authzedbot
added a commit
to authzed/cla
that referenced
this pull request
Jun 23, 2026
miparnisari
approved these changes
Jul 6, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
This PR fixes a grammatical error on the SpiceDB schema concepts page. The sentence was missing the preposition "within" after "found." It now reads correctly as "found within your application."
Testing
This is a documentation-only change. I verified the fix by reviewing the rendered content locally. No functional code changes were made, so no additional testing is required.
References
None