Following how this .net core docs repo issue is handled: https://github.com/dotnet/docs/issues/51274 Verify the resulting corrected messeging is consistent in the aspnetcore.docs repo around this issue.