This is a really great question! I think it’s essential that every member of the team is equally valued. On my last team, the developers referred to themselves as “engineers”. They did not consider testers, designers, POs or customer support people to be “engineers”. But they would use the term “engineers” like “Let’s have a meeting with all the engineers” when they meant everyone on the team. Or they would talk about something the “engineers” needed when the testers needed that thing too.
One way this team tried to be inclusive was with a “thing of the week”. Any non-inclusive behavior or language we wanted to make ourselves more aware of and try to change, we’d make a Thing of the Week. So we made one like this: "When you are talking about the team in general, or people on the team who are in different roles, just use the word ‘team’, not ‘engineers’. It had an effect.
Similarly, remembering to not say “you guys” but instead something like “y’all”, “humans”, “mortals”, “you folks” was an effective Thing of the Week.
Personally I don’t worry about semantics like “testing” vs “checking”, everyone on my teams understands the purpose of regression testing versus exploratory testing and other testing activities. But I’ve run into the “That story is done” quite a bit. I bring this up with the team and ask what we can do to make sure that we don’t say “done” when we mean “done with writing the code - we think”. One team put in big letters across our task board, “NO STORY IS DONE UNTIL IT IS TESTED”. Big visual charts are a great way to help people change their language and thought patterns.