docs: an In the wild block above the headline - #10
Merged
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
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.
Adds a short In the wild callout above the headline, naming a real
deployment and what this crate does in it.
RAG Converter (https://ragconverter.com) lists this crate on its own page; the
wording here is that page's description of the role, not a new claim.
Both files where they differ: the repository README is what GitHub shows, and
the crate's own README is what crates.io renders. Note that crates.io serves the
README from the published
.crate, so the block appears there on this crate'snext release, not on merge.
Documentation only -- no code, no dependency, no version change.