Drop their localization segments, which will result in automatic localization for readers.
Drop versions, which will load the latest version of the topic and thus avoid stale content after 6.0 releases later this year.
UPDATE: I just fixed a new link with a loc segment when resolving a conflict with master. It's best not to include the loc segment (e.g., en-us) for any MS doc cross-link. The loc segment will pin the loaded topic to that language/culture. If it isn't present, the reader gets their localized content ✨ auto-magically ✨.
Hello ...
There's one incorrect link to a Blazor tutorial, which goes to the GH file and not the actual topic. The link to the topic should be ...
https://docs.microsoft.com/aspnet/core/blazor/webassembly-performance-best-practices
Other links can:
UPDATE: I just fixed a new link with a loc segment when resolving a conflict with
master
. It's best not to include the loc segment (e.g.,en-us
) for any MS doc cross-link. The loc segment will pin the loaded topic to that language/culture. If it isn't present, the reader gets their localized content ✨ auto-magically ✨.