The examples were there because they were comparing with
the *original* proposal which was to follow the TPA major release
upgrade schedule. Now that we've ditched that proposal, those examples
are just confusing and make the proposal harder to read.

When this happens the output from needrestart is very unhelpful, so it's
good for us to know what to do with this situation.

This new step really is an eyesore, and we would be better off
automating this. But the issue with bacula-sd not knowing about the new
volumes until we manually restart it is happening quite often. At least
with this added step we'll avoid useless backup errors for new machines.

both are currently just below this section but they're not subsections
so it's a little bit not obvious where to look at. With the links this
becomes a no-brainer

We don't have such a thing as a "preliminary draft" in our process,
otherwise we'd have a lot more in there...

RFC 84 review

See merge request !75