Thanks for taking a look Roy! The answer..: it depends.. We strongly discourage just "fixing" whatever tooling says needs to be fixed. Most of all, we don't want to document all of the APIs, mostly because they might be legacy and either accidentally public, unsupported or scheduled for removal (we have a lot of legacy code that needs removal 😅 so we're taking it slow). However, we have in the past accepted fixes to the C# API documentation, so expanding with examples etc. is indeed just fine, this helps with intellisense as well. In that case I would suggest starting small, with just a few files, to make it a lot easier for the reviewers to evaluate. Does that make sense?