First, use clearer units (GiB instead of G). Then use the k prefix so
it's clearer the connexion between the "1GiB" and the "1024". That way
it's also easy to do, say, a 4GiB swap partition (4k instead of 4096).

back in 9d9aed39 (use <a id=""> instead of name, as name is not HTML5,
2023-06-01) we switched everything to id= but overlooked that id=
actually gets redacted by GitLab's sanitizer. With this, we should be
able to get the anchors through the filter even if it generates
non-conformant HTML5.

It wasn't clear to me reading this who requested the separation in the
first place, now the links should provide a bit more background.

I have briefly considered making a new service document for this, but
I'm tired and I'm not sure it's worth it. I did try to at least nail
something in the installation and pager playbook, along with a basic
howto.

Still incomplete.

Turns out you just can't have pipes in a markdown table... ?

I thought it would export only subkeys and therefore that
export-secret-keys would not, but it's more complicated than that:
export-secret-subkeys exports all secret keys (including the primary)
but in a way that "render the secret part of the primary key useless".

After one too many pipeline failures due to old spell-checking
mistakes, I decided to own up to my stuff and spell check
everything. I actually ran:

     codespell --interactive 3 --write-changes *

And dealt with *almost* all the errors, except stuff in old/ which
I'll remove shortly.

When an error comes up now, it is new and should be fixed.

GitHub now supports deploy keys with write permissions, so there is no
need anymore for a surrogate GitHub account. Using the deploy key allows
for a much simplified setup process, in addition to making each key
project-specific on the GitHub side.

Had this in my git stash, still relevant although I've since migrated
away from PIV tokens