MD docs (specs) : cleanup

[Jay-o-Way]

Fixes

Example for #10951

PR Type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

Description

Many changes to MD files. Starting with only the "Specs" folder. (for now)

For example, but not limited:

• Used "Learn Authoring Pack" in VS Code
• Consolidated lists to use "-" for bullets
• Spelling and grammar errors, and casing (e.g. words like XAML or API must be uppercase)
• A few GitHub style alerts
• Updated all links to point at learn.microsoft.com and removed /en-us/ bits (!)
• Code-blocks should be marked with csharp and not with cs or c#

Motivation and Context

A company as big as Microsoft should have perfect documentation.

How Has This Been Tested?

• I have performed a self-review of my own code
• I have added tests to cover my changes

Extra:

Important

Document-specific points of attention:

in AnimatedVisualPlayer Spec

• AnimationOptimization versus AnimationsCacheMode
• table: "Latency" and "Resources", text: "Always" and "None"

in custom-iresourcemanager-spec

• API details: CustomResourceManager versus Resource

in FooterMenuItemTemplate-spec

• FooterMenuItemSource versus FooterMenuItemsSource → typo?

in NavigationViewTemplateSettings-OpenPaneLength

• OpenPaneLength="{Binding ... TemplateSettings.OpenPaneWidth}" should be OpenPaneLength

[Jay-o-Way]

Any advise for the attention points? @Zakariathr22

[Zakariathr22]

@Jay-o-Way
My suggestion is to keep the cleanup you’ve already done and address the other points in separate PRs, as those points require review and alignment with the maintainers.

[Jay-o-Way]

Okay I see. So what's the hold on this one? The longer a PR stays open, the more chance of merge conflicts. And I don't like those 🤓