Previous link expected a label called "T: bug" and "release-notes, which
no longer seem to exist. They were respectively converted to "type:
task" and "release notes" (without dash)
The incidental urlencoding (removal of some '+' should not make a
difference as far as links are concerned).
Following the doc migration from Markdown to RestructuredText, a more
logical markup was applied to the *Features* section, but not to the
section about *video tours*, *screenshots* and *Getting started*. I
changed that last section and ended up using a definition list also for
the Features section (seems more consistent and appropriate as links are
allowed in titles.
The `figure` markup should be used for images with a caption or a
description**
Most of the links have been replaced by their forum counterpart.
I wasn't able to find a few links like "Template: Ubuntu", so I removed
them, because the link is pointless anyway.
Changing `bash` lexer to `console` because it is appropriate most of
the time. Then after a manual review, some lexer have been changed.
I used `text` each time I was unsure, and for prompt outputs.
The page `/developer/building/qubes-iso-building.rst` still need to be
reviewed (look for lines starting with `$ #`).
I'm not sure about the Windows pages, should we use
[doscon](https://pygments.org/docs/lexers/#pygments.lexers.shell.MSDOSSessionLexer)
or `powershell`?
Is there an appropriate lexer for `guid.conf` content?
**Statistics - Before**
870 bash
9 python
9 c
2 yaml
**Statistics - After**
684 console
111 text
44 bash
16 yaml
9 systemd
9 c
8 python
4 ini
4 doscon
2 markdown
2 desktop
1 xorg.conf
1 xml+jinja
1 xml
1 kconfig
1 html
This suggests that the default lexer should be `console`.
This is plain rename without changing content, to help git track files
history.
Do not touch files that are going to be removed during conversion.
Thanks @parulin for the idea!
