

How do you usually deal with that aspect? What I do is to make the documentation easily skimmable (for advanced readers) and just accept the need for rework.
Confluence’s “Expand” element. Make everything into an easy to read task-list, but if more details are necessary, just expand a step and get an “idiot proof” description. Bookstack allows that as well, even better, because you can nest them (Confluence had that up until they “updated” the editor and killed half the features).
EDIT: “Include Page” in Confluence also works wonders here. For example, I have an article describing how to RDP to our AD server. In all articles that describe a process that needs to be done on the AD server, I just include that page. If any connection details change, I just edit the original article and the changes immediately propagate to all the other instances.
Wellllll, I wouldn’t go that far.
I just had to reboot because clicking anything in the browser randomly started sending the CPU utilisation to higher 70s, which was triggering the fans to spin at full power.
Then I ran a game on Steam and Steam said it’s running, but it was nowhere to be found. Had to reboot again.
Both of these happened completely randomly after I changed nothing, just browsing the web.