I have in the past, about 4-5 years ago found some aspects of documentation on MDN in the examples that did not work in browsers because not implemented at the time, as well as some lack of clarity in documenting differences between fit-content function and fit-content keyword therefore I raised an issue https://github.com/mdn/sprints/issues and got the documentation amended. However of course that no longer works for the reasons already mentioned, not sure if there is some other place or process whereby you can raise issues and get documentation changed.

on edit: the issue, 5 years ago https://github.com/mdn/sprints/issues/3723

Thanks so much for sharing this — and for taking the time to raise those issues back then! <3

You're absolutely right that the old `mdn/sprints` repo is no longer the active channel for suggesting or discussing content changes. These days, we encourage folks to file issues directly in the mdn/content¹ GitHub repository. That’s where all our documentation now lives, and it’s actively maintained by MDN staff and contributors.

If you spot inaccuracies, outdated examples, or unclear distinctions on any page, we now have a way to report straight from the page, you can find this at the bottom of every page → "Report a problem with this content." Please feel free to open an issue² or even suggest edits directly via pull request. We also try to prioritize fixes based on how widely used or confusing a topic might be, so calling attention to edge cases or under-documented differences is genuinely helpful.

Let me know if you’d like help filing an issue or want to connect with the folks maintaining a specific area of the docs. We’d love to have you involved again!

¹ https://github.com/mdn/content ² https://github.com/mdn/content/issues/new/choose

Thanks for sharing. The best place to raise issues now is the content repo: https://github.com/mdn/content