GitLab

The old welcome_screen.png from 4.8 still displays the "Beta" warning
and says that only the Unsafe Browser setting is persisted, which is
not the case in 4.11.

And fix very old typo 'is' → 'if'!

- We've had 2 places to document manual upgrades since 2016,
  /doc/upgrade then pointing to /upgrade for the actual meat. Having a
  single place prevents people to jump around needlessly.

- Tails Upgrader has been pointing to /doc/upgrade since 2014 and these
  old versions of Tails will continue to point to it.

- We could as well redirect /doc/upgrade/#manual to /upgrade but
  /doc/upgrade has the advantage of putting both techniques in
  perspective.

- /doc/upgrade (formerly /doc/first_steps/upgrade) is very well indexed
  by search engines while we prevented /upgrade to be indexed by
  'noindex'.

Currently translated at 17.7% (11 of 62 strings)

Translation: Tails/wiki/src/news/version_3.14.1.*.po
Translate-URL: http://translate.tails.boum.org/projects/tails/wikisrcnewsversion_3141po/pt/

Currently translated at 39.0% (16 of 41 strings)

Translation: Tails/wiki/src/news/version_3.11.*.po
Translate-URL: http://translate.tails.boum.org/projects/tails/wikisrcnewsversion_311po/it/

"Changes" has a probably stronger meaning as the first word in the title
when put in parallel with "[New] features" and "[Fixed] problems".
Upgrades are one type of changes.

This "Change" section doesn't bring much and look especially weird in
short release notes.

It's probably less dangerous and confusing to show upgrade first to
people who want to install than to show install first to people who want
to upgrade as they could erase their persistence is their follow the
installation instructions

- Separate them more
- Clarify the impact on persistent storage
- Put on the same level as download only in release notes

It's usually the longest one.