I love moving to inclusive naming of things in tech.
Not only is "Allowlist/Blocklist" (or equivalent) more inclusive than "whitelist/blacklist", it also makes it that much more clear what putting something on the list actually does.
Same with Master branches on code repositories - what does that even mean? It's not actually ruling over any other branches, it's just the main code trunk all of the others are branching off of. Calling it "master" just makes it more confusing.
Same with "master/slave" databases - Active/standby is going to be more clear about the roles and responsibilities of the various servers.
@JessTheUnstill This is one of the points that I really like to underscore: changing for inclusiveness and accessibility is sufficient, but the new names are also often _so much better_.
"Master/slave" not only is problematic, but as you point out it _makes no sense_ with how these systems are used in practice, and much clearer naming is available.