That's not really an example of what they're bringing up.
Microsoft has the .Net ecosystem (as the above poster described it "Microsoft's Java," which it largely is). However for a period Microsoft was naming other products and services ".Net" that were completely unrelated. Specifically this: https://en.wikipedia.org/wiki/Microsoft_.NET_strategy
Both .Net Core and .Net Standard are part of the .Net ecosystem for real, making them not an example of the marketing phenomenon being discussed here. Which isn't to say the names aren't confusing, just that it isn't in the same pattern.
PS -
.Net Framework: Legacy/Classic .Net. Windows Only. Started in 2002. 4.8 is the final major version.
.Net Core: Light weight/cross platform "reboot" of .Net Framework. Started in 2016.
.Net Standard: Minimum subset of both that allows libraries to be cross-compatible with .Net Framework and .Net Core. Also assures they lack Windows specific dependencies. Allowing a bridge to migrate to .Net Core.
Microsoft has the .Net ecosystem (as the above poster described it "Microsoft's Java," which it largely is). However for a period Microsoft was naming other products and services ".Net" that were completely unrelated. Specifically this: https://en.wikipedia.org/wiki/Microsoft_.NET_strategy
Both .Net Core and .Net Standard are part of the .Net ecosystem for real, making them not an example of the marketing phenomenon being discussed here. Which isn't to say the names aren't confusing, just that it isn't in the same pattern.
PS - .Net Framework: Legacy/Classic .Net. Windows Only. Started in 2002. 4.8 is the final major version.
.Net Core: Light weight/cross platform "reboot" of .Net Framework. Started in 2016.
.Net Standard: Minimum subset of both that allows libraries to be cross-compatible with .Net Framework and .Net Core. Also assures they lack Windows specific dependencies. Allowing a bridge to migrate to .Net Core.