Even with fairly up-to-date packages, many Linux distributions have not
recent enough Python Protobuf packages. It's better to use the PyPI
package, which is published by Google, rather than the distribution
packages.
Ideally, adevtool could handle this (with pinned package version and
hash, and hash-checking), but due to many users encountering this issue,
this change should be reasonable for now.
We want to link to this section. The nesting is a little too deep, but
it's the simplest solution for the given state. Ideally, the structure
will be generally flatter and reorganized.
Co-authored-by: matchboxbananasynergy <107055883+matchboxbananasynergy@users.noreply.github.com>
After installation, the user may want to dive into more information
about the new system they got (=> "Further information"). This should
have a higher priority than the section "Replacing GrapheneOS with the
stock OS."
The changes summarized:
* Use angle brackets (`>`) instead of arrow symbols (`➔`).
* Put a non-breaking space (` `) before each angle bracket.
* Wrap sequences and elements in bold element (`<b>`).
* Accessibility: Wrap angle bracket in a span tag with an aria-label.
References:
* https://developers.google.com/style/procedures#multi-action-procedures
* https://developers.google.com/style/ui-elements#angle-brackets
I use the entity number ` ` for the non-breaking space instead of
the named character entity ` ` because `xmllint` produces a linting
error (which is to be expected).
```
parser error : Entity 'nbsp' not defined
```
Ideally we want to use the named character entity (` `), but I
couldn't find a reasonable solution. In order not to block this change,
I've opted for the entity number (` `). If a reasonable solution is
found, the entity number can be easily replaced by the named character
entity.
The changes require more than just replacing the currently used arrow.
The surrounding context should be checked to determine whether a change
is appropriate at this point and whether it requires further changes in
the context itself.
The paragraphs are wrapped with the currently used 98 characters. If
using vim:
```
:set tw=98
```
Vim's wrapping is weird when applied several times. To work around this,
we can unwrap the paragraph first. To select a paragraph, unwrap and
rewrap: Point to the line of the paragraph, and type `vipJgqq` in normal
mode.
