@microsoft-github-policy-service agree

How about renaming New Text File in the menu bar to New Untitled File? The command's id is 'workbench.action.files.newUntitledFile', so changing the display name to New Untitled Text File puts it out of sync with the id (unless we change the id as well). It also looks like the term New Text File is only used in the menu bar.

Another benefit is that Compare New Untitled Files is a word shorter than Compare New Untitled Text Files!

No, we cannot. The current wording in the menu was part of an effort to make things more discoverable and understandable if I remember correctly.

To clarify renaming New Untitled File to New Untitled Text File, a few questions:

• Does this mean every instance where the term shows up, or only the command label?
• How should variable names be handled (change NEW_UNTITLED_FILE_COMMAND_ID to NEW_UNTITLED_TEXT_FILE_COMMAND_ID, same with NEW_UNTITLED_FILE_LABEL)?
• Do command ids also merit a change, like 'workbench.action.files.newUntitledFile'?

A few examples of other instances:

Yes, I suggest to change user facing labels, but we cannot change command IDs for backwards compatibility. I think leaving variable names as they are is also fine, but feel free to change them if you feel strong about it.