It was brought to my attention on twitter that there was a patronizing tone in the documentation for compose that 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 use pipe over compose and needed to be altered.
This PR replaces the paragraph for compose to 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 both pipe and compose while I was in there.
Coverage remained the same at 100.0% when pulling 9ac1c6efdc9d37b611acee28d9ab119a241ac7ef on docs/more-inclusive-language into e8935b1d641300dca59d1a1ac62e13aed0345c90 on master.
Not cool
It was brought to my attention on twitter that there was a patronizing tone in the documentation for
compose
that 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 usepipe
overcompose
and needed to be altered.This PR replaces the paragraph for
compose
to 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 bothpipe
andcompose
while I was in there.