Should it be fixed for 1.22 @gregvanl?

I pushed some changes to master (1.23).
Now there's a validation error if you still use 'Languages' in categories.
So for a better user experience, we should push the change to 1.22 as well.

I will update the vscode-generator-code as soon as the change is in a stable build.

I pushed a improvement that 'Languages' only gets a deprecated warning (not an error). So no need to rush this in 1.22.

Also pushed changes to our yeoman generator.

Marking as fixed. @gregvanl Do you coordinate the other changes?
That's what I imagine:
In the marketplace: Covert all published extensions that use 'Languages' to use 'Programming Languages'
Give good error feedback when trying to publish an extension still using 'Languages'

@aeschli I haven't been coordinating this, I just heard from @seanmcbreen about the change with respect to the docs and figured we'd need to change the product to match. I'm not sure what further work the Marketplace has planned for updating existing extensions or providing feedback.

Verifiers:
Create an extension that uses the old keyword ('Languages') and verify that you get a warning.