Cmdlets for FODs and "Windows Features" lacking specificity

[AdreKiseque]

Prerequisites

• Existing Issue: Search the existing issues for this repository. If there is an issue that fits your needs do not file a new one. Subscribe, react, or comment on that issue instead.
• Descriptive Title: Write the title for this issue as a short synopsis. If possible, provide context. For example, "Typo in Get-Foo cmdlet" instead of "Typo."
• Verify Version: If there is a mismatch between documentation and the behavior on your system, ensure that the version you are using is the same as the documentation. Check this box if they match or the issue you are reporting is not version specific.

Links

• https://learn.microsoft.com/en-us/powershell/module/dism/get-windowscapability
• https://learn.microsoft.com/en-us/powershell/module/dism/add-windowscapability
• https://learn.microsoft.com/en-us/powershell/module/dism/remove-windowscapability
• https://learn.microsoft.com/en-us/powershell/module/dism/get-windowsoptionalfeature
• https://learn.microsoft.com/en-us/powershell/module/dism/enable-windowsoptionalfeature
• https://learn.microsoft.com/en-us/powershell/module/dism/disable-windowsoptionalfeature

Summary

The -WindowsOptionalFeature and -WindowsCapability cmdlet groups in the DISM module lack a few details in what exactly they target, which notable since the names don't quite match up with what one might expect.

Details

These cmdlets manage Features on Demand (FODs) and "Windows Features", two distinct package types. They aren't entirely clear on this, though, with extra confusion stemming from the fact that FODs are managed in the Settings app under an "Optional Features" tab (with "Windows Features" in a Control Panel menu accessible from that tab through a button labelled "More Windows features"), but the -WindowsOptionalFeature cmdlets actually manage the other set, while it's the -WindowsCapability cmdlets that manage FODs.

This all likely stems from a deeper issue with inconsistent nomenclature in DISM and the like, and in fact I'd argue the other DISM cmdlets could use some more details as well. But the way these have conflicting names makes them stick out to me.

Suggested Fix

Short notes explaining what the items managed by the cmdlets are called in other places would be an easy improvement. Including links to documentation pages that further discuss the different package types would also make it much easier to grasp what the different cmdlets are for.