Page Cache Aliases – misnomer?

Hi,

I previously had an issue with translations not being purged from the cache when doing a purge-single-item. Your suggestion was to add the domain url with the language slug to the aliases field and enable aliases. This works well indeed, thanks. Now the translations get purged too. So great support and solution.

However: the “aliases” entry looks like a complete misnomer to me, as it creates confusion with a real website “alias”, which would need a 301 in the real world. In fact, on the web you can find many articles about W3TC setup which state “don’t use, do a permanent redirect instead”. ??
This was one of the reasons I never thought about this as a solution for the translations purge.

Anyway, I would like to put this question to you:
Would it not be better to change the > Page Cache > Aliases name and description to something more accurate? Because it really isn’t an alias at all, it is much more a “cache-linked domain” or a “content-linked url” or something like that.

I think that this would maybe take away much of the confusion about this field/setting.
The description could also hold a line about being used for URL-with-language-slug for translations maybe?

Just a thought, what do you think?
Rob