Is this the right way to request a Doc update?

[HansLachman]

I filed the following requests for Documentation updates:

(2025.11.22) Need warning that, in dual-boot, Grub OS menu might not appear
linuxmint/doc-installation-guide#17

(2026.04.06) Need to update minimum disk space in Installation Guide
linuxmint/doc-installation-guide#20

(2026.04.06) Need to update minimum disk space in the FAQ
linuxmint/linuxmint#861

Is filing the above issues the right way to request Documentation updates?

Also, is it also a good idea to post this inquiry here in "linuxmint/discussions"? The suggestion that I post this inquiry here was offered to me by someone on the Linux Mint forum ( https://forums.linuxmint.com/viewtopic.php?p=2719608#p2719608 ). Please note that the first item above is a few months old and hasn't been "assigned" yet. I don't know if anyone has looked at it.

Additionally, I would like to offer my opinion that my requests may be "low hanging fruit", i.e., easy to make the updates and perhaps useful to end users.

Also, I'm aware of suggestions that users can become contributors, and perhaps I could make the fixes myself (e.g., https://github.com/orgs/linuxmint/discussions/919 ), but I've never contributed code updates or doc updates on open source before, so I might have a learning curve. Thanks.

[shreyanshjain1]

Yeah, I’d say that filing issues in the relevant repo is the right way to request doc updates.

From what you listed, opening issues against the actual docs repo / relevant Mint repo makes sense, since it gives the maintainers something trackable and specific to review.

And posting here in Discussions also seems totally reasonable, esp since you were pointed here from the Mint forum and your question is more about process than about one specific doc bug.

So imo:

• issues = best place for the actual doc change requests
• discussion = fine for asking whether you’re using the right process, or for getting maintainer/community guidance

Also, I wouldn’t worry too much if an older issue hasn’t been assigned yet. In a lot of open source projects, unassigned doesnt always mean ignored, sometimes it just means nobody has formally picked it up yet.

And honestly, the kind of changes you’re describing do sound like useful low-hanging-fruit doc fixes.

If you ever do want to contribute directly, doc updates are actually one of the nicer ways to start contributing, since the barrier is usually lower than code changes. But even just filing clear issues like you already did is still helpful.

So yeah — I’d say you’re using a reasonable path here.