Add xref API doc links to maui/markup/markup.md

[Copilot]

MAUI API docs are now published, so xref links can be added to Microsoft.Maui.* types referenced in the markup documentation.

Changes

• Prose text: Linked first mentions of Grid, Label, Entry to their API docs
• Converters section: Linked IValueConverter and IMultiValueConverter
• Extensions table: Linked all MAUI type references in descriptions — View, AbsoluteLayout, BindableObject, Binding, Element, FlexLayout, Image, IImage, ItemsView, CarouselView, CollectionView, Label, IPlaceholder, Style, ITextAlignment, VisualElement

Format follows existing convention in the repo:

[`View`](xref:Microsoft.Maui.Controls.View)
[`IImage`](xref:Microsoft.Maui.IImage)

Types left unlinked: IDynamicResourceHandler (internal API, no public docs), Grid on line 121 (not in backticks in original), property names like EmptyView/Margin/HorizontalTextAlignment.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Include API doc links</issue_title>
<issue_description>Currently it is not possible to include any xrefs to Microsoft.Maui.* because the API docs for MAUI have not been published.

This is here to remind us that when those docs do we published we should go through the docs pages and fix up any places where an xref should be made.

Current known pages are:

• maui/markup/markup.md</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Include API doc links #15

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[learn-build-service-prod]

Learn Build status updates of commit bf3def1:

⚠️ Validation status: warnings

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions 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.

[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 8a2b1df:

✅ Validation status: passed

File	Status	Preview URL	Details
docs/maui/markup/markup.md	✅Succeeded	View

For more details, please refer to the build report.