You just linked to the answer to your own question. I included the reason in the commit message:
Reason: QubesOS/qubes-issues#6585 has been closed as fixed, and the
update has been in the stable repo for over two weeks.
This was in response to a request from another user:
Edan-Redmind:
@andrewdavidwong I see that your explanation regarding this issue and how to handle it is still on the “How to update” page (How to update | Qubes OS). If the issue is solved then maybe it is best to remove it in order to avoid confusing users who don’t know it is resolved.
Me:
Thank you for the reminder! However, I’m not sure if the fix has migrated to the stable repos yet. If it has not, then stable users will still need the workaround instructions until they receive the update. Usually our bot posts automated comments here when the relevant packages migrate to different repos, but I don’t see any such comments here (yet).
(…about a month later…)
Me:
Ok, since it looks like the update has been in the stable repo for a while now, I’ve removed that text from the doc page.
(This reminds me of a comic strip – I think it was a Ziggy – where he wishes upon a star, but it turns out someone in Toledo just wished for the exact opposite. )
The commands were there as a workaround to a specific bug. The specific bug has been fixed (we think), so the workaround is no longer needed.
Obligatory xkcd:
Because they are no longer necessary. We don’t want to make unnecessary work for users or confuse them into thinking the workaround is still required after the bug it was working around has been fixed.
I don’t think that’s true. The links to those pages are “deep links” (i.e., section anchor links) that take you directly to the required commands. So you don’t actually have to read any more than you did before. You just have to click two links, which I don’t think is too much to ask. (Actually just one, since they’re conveniently right next to each other. ) Besides, duplicating that content was always intended as a temporary kludge, since content duplication is not a sustainable approach.
I guess maybe you didn’t try clicking either of those links, or maybe the autoscrolling didn’t work for you. When I click on them, it takes me directly to explicit example commands:
update.qubes-dom0
Updates dom0. Example (executed in dom0):
$ sudo qubesctl --show-output state.sls update.qubes-dom0
update.qubes-vm
Updates domUs. Example to update all templates (executed in dom0):
$ sudo qubesctl --show-output --skip-dom0 --templates state.sls update.qubes-vm
If the complaint is about having to click an extra link, remember that you can instead just bookmark the first link, so you only have to click once.