Remove patronizing tone from documentation #466
Merged
Conversation
This file contains 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
evilsoft
changed the title
pipe shaming language from documentation
dalefrancis88
approved these changes
Mar 16, 2020
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.
Not cool
It was brought to my attention on twitter that there was a patronizing tone in the documentation for
composethat was not very inclusive . After it was reported and I read through it, I determined that it was indeed needlessly "shaming" and being overly patronizing to a person on their preference to usepipeovercomposeand needed to be altered.This PR replaces the paragraph for
composeto just provide information on the relationship between the two. Removing the non-inclusive, shamming voice from what should be a more neutral tone. I also added some similar examples for bothpipeandcomposewhile I was in there.