nadworks
Active Member
Hi, this is a minor issue which I've been ignoring for a while, but a couple of my clients have also started mentioning it now.
On many backend field descriptions and examples, the subscribers and users are exclusively referred to as "he" and "him".
There are frequent examples - here's just one of them:
I know some of you might roll your eyes now. But it really sticks out like a sore thumb and is just quite a bit behind the time now. As I'm onboarding more and more clients, it will become a problem and since we're hosting the platform, the unease will be addressed at us.
Maybe there's an easy enough way of finding/replacing these with gender-neutral language "they" and "them" for the next release.
On many backend field descriptions and examples, the subscribers and users are exclusively referred to as "he" and "him".
There are frequent examples - here's just one of them:
I know some of you might roll your eyes now. But it really sticks out like a sore thumb and is just quite a bit behind the time now. As I'm onboarding more and more clients, it will become a problem and since we're hosting the platform, the unease will be addressed at us.
Maybe there's an easy enough way of finding/replacing these with gender-neutral language "they" and "them" for the next release.
