Update markdownlint rules

[sdwheeler]

PR Summary

Update markdownlint rules

• Fixes AB#548067

PR Checklist

• Descriptive Title: This PR's title is a synopsis of the changes it proposes.
• Summary: This PR's summary describes the scope and intent of the change.
• Contributor's Guide: I have read the contributors guide.
• Style: This PR adheres to the style guide.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[Copilot]

Pull request overview

This PR updates markdownlint rules by removing legacy docsmd.* rules, adding new rules (MD054-MD060), and fixing spelling errors in comments. The changes aim to modernize the markdownlint configuration to support newer linting rules for tables, links, and images.

Changes:

• Removed 12 docsmd.* custom rules that were previously defined at the beginning of the file
• Added 6 new standard markdownlint rules (MD054-MD060) for link/image styling, table formatting, and descriptive link text
• Fixed spelling errors in comments: "Superceded" → "Superseded" (2 occurrences)

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[learn-build-service-prod]

Learn Build status updates of commit eba3e42:

✅ Validation status: passed

File	Status	Preview URL	Details
.markdownlint.yaml	✅Succeeded

For more details, please refer to the build report.

[learn-build-service-prod]

PoliCheck Scan Report

The following report lists PoliCheck issues in PR files. Before you merge the PR, you must fix all severity-1 and severity-2 issues. The AI Review Details column lists suggestions for either removing or replacing the terms. If you find a false positive result, mention it in a PR comment and include this text: #policheck-false-positive. This feedback helps reduce false positives in future scans.

✅ No issues found

More information about PoliCheck

Information: PoliCheck | Severity Guidance | Term
For any questions: Try searching the learn.microsoft.com contributor guides or post your question in the Learn support channel.

[learn-build-service-prod]

Learn Build status updates of commit a9a375a:

✅ Validation status: passed

File	Status	Preview URL	Details
.markdownlint.json	✅Succeeded
.markdownlint.yaml	✅Succeeded

For more details, please refer to the build report.