Minor improvement to linker descriptor documentation

[mrvoorhe]

The Assembly. part in lines such as

    <type fullname="Assembly.B" />

Could be confusing. While it is convention to have the assembly name and namespace match, it's not a requirement.

[mrvoorhe]

@sbomer Please take a look

[dotnet-policy-service]

Tagging subscribers to this area: @agocke, @dotnet/illink
See info in area-owners.md if you want to be subscribed.

[Copilot]

Pull request overview

Updates the ILLink linker descriptor documentation examples to avoid implying that a type’s namespace must match the assembly name, reducing confusion for users writing descriptor XML.

Changes:

• Replaced Assembly.* type fullname examples with Namespace.* to better reflect that type names are namespace-qualified, not assembly-qualified.
• Adjusted multiple XML snippets throughout the doc to consistently use the new placeholder namespace.

[Copilot]

In this example, the comment says the type name matches a “regular expression”, but the sample uses the * wildcard pattern (as in the earlier prefix examples). Also, <type fullname="Namespace.Namespace*" /> and <namespace fullname="Assembly.Namespace" /> use different prefixes, which undermines the doc’s goal of showing assembly name and namespace aren’t inherently related. Consider updating the wording to describe wildcard matching and aligning the sample namespace/type values.

[Copilot]

Typo in the comment: “who's” should be “whose”.

Suggested change

	<!-- Preserves all types who's fully qualified type name matches the regular expression -->
	<!-- Preserves all types whose fully qualified type name matches the regular expression -->

[Copilot]

This line (and a few others in the XML snippets) has trailing whitespace at end-of-line. In Markdown this can create unintended hard line breaks and also tends to fail whitespace hygiene checks; please trim trailing spaces in the examples.

[mrvoorhe]

@sbomer Can you merge this?

[JulieLeeMSFT]

@mrvoorhe, please address the copilot reviews.
cc @sbomer.