docs: align use-case claims and plainify prose - #56
Merged
Conversation
Remove the constructions that read as machine-written: the cleft "X is what Y" sentences, the "X, not Y" closers, the concessive "that is less code and it works", the anthropomorphic "that example wants three things", and aphorisms such as "Sequential does not mean once". Every technical claim, guarantee, benchmark number, policy name, and code sample is unchanged. Prose only.
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.
Two documentation commits, no code changes.
docs: align use-case claims with the JS port— brings the Rubyuse-case wording in line with the JS port, matching
docs: align use-case claims with the Ruby gem solid-objects-js#30.
docs: use plainer prose in README and guides— removes therhetorical constructions that read as machine-written.
What the prose pass changed
Validation
Markdown only. No Ruby source, signature, migration, or test file is
touched, so
rakebehavior is unchanged. Every guarantee, benchmarknumber, policy name, and code sample is preserved verbatim.