Turns out that using non-historically loaded language is actually easier to understand than the current mainstream.
White/black list? Awkard, not obvious if you don't have "white: OK, black: KO" internalised.
Master/[slave|servant]? Awkward, not obvious if you aren't used to absolute, totalitarian and static power dynamics.
allow/deny list is simple, direct, descriptive.
[main|primary]/secondary is simple, direct, descriptive; and is more dynamic.
It's easy to imagine things that are "primary" in certain contexts and "secondary" in others, while "master/slave" has a hint of... immutability to it.
And this is not crazy talk, things like the amazingly good Knot DNS server struggle to explain this in their documentation:
If you replace "master" with "primary" and "slave" with "secondary", suddenly the fact that this authority is relative to each zone becomes much easier to explain (and understand).
And just as a reminder: you don't have to change all the things at once, step-by-step incremental change compounds and goes a long way.
It's also fine to make mistakes and correct them, see this recent-enough example:
chaos.social – a Fediverse instance for & by the Chaos community