Feature/win2dparser for CanvasPathGeometry and Win2D Path Mini Language

[michael-hawker]

Finishes #392

Docs for Toolkit PR #3503

What changes to the docs does this PR provide?

Rebases and cleans-up the linter/warnings from the doc build.

PR Checklist

Please check if your PR fulfills the following requirements:

• Correctly picked the right branch to base the change off (master for new features, live for typos/improvements)
• For new pages, used the provided template
• For new features, added an entry in the Table of Contents
• Ran against a spell and grammar checker
• Contains NO breaking changes

Other information

[opbld30]

Docs Build status updates of commit acf66b5:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/.template.md	✅Succeeded
docs/brushes/AcrylicBrush.md	✅Succeeded	View
docs/brushes/PipelineBrush.md	✅Succeeded	View
docs/brushes/TilesBrush.md	✅Succeeded	View
docs/parsers/CanvasPathGeometry.md	✅Succeeded	View
docs/parsers/Win2D_Path_Mini_Language.md	✅Succeeded	View
docs/platform-specific/PlatformSpecificAnalyzer.md	✅Succeeded	View
docs/platform-specific/PlatformSpecificDifferencesGenerator.md	✅Succeeded	View
docs/resources/images/Squircle.gif	✅Succeeded	View
docs/toc.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[opbld30]

Docs Build status updates of commit d04a405:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
docs/parsers/Win2D_Path_Mini_Language.md	⚠️Warning	View	Details
docs/.template.md	✅Succeeded
docs/brushes/AcrylicBrush.md	✅Succeeded	View
docs/brushes/PipelineBrush.md	✅Succeeded	View
docs/brushes/TilesBrush.md	✅Succeeded	View
docs/parsers/CanvasPathGeometry.md	✅Succeeded	View
docs/platform-specific/PlatformSpecificAnalyzer.md	✅Succeeded	View
docs/platform-specific/PlatformSpecificDifferencesGenerator.md	✅Succeeded	View
docs/resources/images/Squircle.gif	✅Succeeded	View
docs/toc.md	✅Succeeded	View

docs/parsers/Win2D_Path_Mini_Language.md

• Line 30, Column 3: [Warning-bookmark-not-found] Cannot find bookmark '#introduction' in 'parsers/Win2D_Path_Mini_Language.md'.

For more details, please refer to the build report.

If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel

[opbld31]

Docs Build status updates of commit d2bd6ad:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/.template.md	✅Succeeded
docs/brushes/AcrylicBrush.md	✅Succeeded	View
docs/brushes/PipelineBrush.md	✅Succeeded	View
docs/brushes/TilesBrush.md	✅Succeeded	View
docs/parsers/CanvasPathGeometry.md	✅Succeeded	View
docs/parsers/Win2D_Path_Mini_Language.md	✅Succeeded	View
docs/platform-specific/PlatformSpecificAnalyzer.md	✅Succeeded	View
docs/platform-specific/PlatformSpecificDifferencesGenerator.md	✅Succeeded	View
docs/resources/images/Squircle.gif	✅Succeeded	View
docs/toc.md	✅Succeeded	View

For more details, please refer to the build report.

Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.

For any questions, please:

• Try searching the docs.microsoft.com contributor guides
• Post your question in the Docs support channel