Not just you! I'm looking for the link as well, and looks like it's just an image.

I think I've learned to get less attached to opinionated terminology in code and database design because I see it happen all the time where the usage of the value/field/thing can evolve naturally over time as the business needs evolve. And refactoring field names (as an example) from UI to database is often a painful exercise, not without significant regression risks. (Depending on the size and complexity of your systems, of course)

So while I totally agree with you and others that ideally naming would be consistent throughout, my real world experience with the issue has taught me that this isn't the hill I die on.

My 2 cents from 10 years experience in the industry.