feat: adopt inclusive language within published blog posts

[fladson]

Closes #707

[dblandin]

This is a good start! I think we might want to hold off on merging until we can align on the best way to retroactively make these changes while also being respectful of/to the original content/author.

[kathytafel]

Hey @pepopowitz maybe you can chime in here. In the past I've used [editorial brackets] to indicate a change. We could make an asterisk on it. Or make a note like Disney does on Peter Pan.

[dblandin]

Some of the target language is found in code examples which might be difficult to add editorial markings to.

I'd also support some sort of "Editor's Note" at the bottom of each affected post. Maybe something like:

Editor's Note: This post has been updated as part of an effort to adopt more inclusive language across Artsy's GitHub repositories and editorial content (RFC / PR).

Or perhaps "...as part of a commitment to adopt more inclusive language..."?

[orta]

( You have my permission to omit the editor's notes on my posts, which I think makes the majority of these changes )

[kathytafel]

That makes it easy, @orta. Thanks!

[pepopowitz]

I think these are all good suggestions -- but I also don't think anyone would be too mad if we just changed these all and didn't add a note. Barring any objections, I'm planning to merge this as-is by the end of the day.

[kathytafel]

I just noticed that it's a CC4 license. Still onboarding. I'm ok with no note and just changing everything given the license.

[pepopowitz]

Since a similar conversation came up in #711, I decided to add a footer based on @dblandin's comment to each of the updated articles.

@dblandin I'm going to assign this PR to you, to confirm that (a) your requested changes are resolved and (b) the footer looks good.

An example of the footer:

[dblandin]

Looks great!! 💯