Gregory's Server
@davidaugust One of the unfortunate things is that until not so long ago, it used to be relatively standard to quite literally build the manual into the software (along with the printed version also existing).
At some point as the web became more common, that habit got dropped. And since sites & links routinely die, the replacement of "just go on the site" is terrible (nevermind other common connectivity problems, which is even more "fun" when a router has that problem).
@lispi314 agreed. I get that maintaining a single documentation location is easier and less expensive for those building a system, but the users need it available wherever they look whenever they look. I prefer inline but not cluttering documentation as it is convenient for users (most of the time) and if something is changed that something’s documentation is right there obviously needing change too. Your connectivity example is a use case that really demands no remote resource be needed.