nvim-devdocs VS dotnet-api-docs

I've been using DevDocs in Neovim through this plugin: https://github.com/luckasRanarison/nvim-devdocs

Works great, and don't ever have to leave my editor to read something

Certain parts of Microsoft Learn are permissive, for example the .NET BCL documentation is Creative Commons Attribution: https://github.com/dotnet/dotnet-api-docs as is ASP.NET Core: https://github.com/dotnet/AspNetCore.Docs (a good hint if documentation is permissively licensed and on GitHub is if there's an edit button at the top.)

The C# language specification is unfortunately a bit fuzzier: https://github.com/dotnet/csharplang/discussions/4855

The updated unified C# language specification is CC, but it's still catching up to modern C#: https://github.com/dotnet/csharpstandard

Oopsie. I created an issue on GitHub for it as well (link), but at the moment of writing this article there was no news on it.

The docs are also under source control. There is even an edit link on the doc page that takes you straight to GitHub. Instead of wasting time whinging on the internet why not submit a PR to fix it?

https://docs.microsoft.com/dotnet/api/ is the language agnostic link and latest version link (always redirects to latest version of .NET and your machines culture.

I would suggest posting an issue to dotnet-api-docs regarding the poor discoverability of relevant design/introduction articles written by MS team members from within the API docs themselves. If you are suggesting more samples for Channel, then open an issue for that, too. After checking for duplicates.