Git-Mirrors/qubes-doc
1
0
Fork 0
mirror of https://github.com/QubesOS/qubes-doc.git synced 2025-08-22 13:39:36 -04:00
Code Issues Projects Releases Packages Wiki Activity

Misc. text cleanup and updates

Browse source
This commit is contained in:
Andrew David Wong 2023-08-10 15:25:25 -07:00
parent 5dec150eec
commit 87d52d4a85
No known key found for this signature in database
GPG key ID: 8CE137352A019A17
1 changed files with 8 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

17
user/how-to-guides/how-to-update.md
View file

@ -14,8 +14,8 @@ looking to upgrade from your current version of Qubes OS to a newer version,
see the [Upgrade Guides](/doc/upgrade/).* see the [Upgrade Guides](/doc/upgrade/).*
It is important to keep your Qubes OS system up-to-date to ensure you have the It is important to keep your Qubes OS system up-to-date to ensure you have the
latest [security updates](#security-updates), as well as the latest latest security updates, as well as the latest non-security enhancements and bug
non-security enhancements and bug fixes. fixes.
Fully updating your Qubes OS system means updating: Fully updating your Qubes OS system means updating:
@ -26,8 +26,8 @@ Fully updating your Qubes OS system means updating:
## Security updates ## Security updates
Security updates are an extremely important part of keeping your Qubes Security updates are an extremely important part of keeping your Qubes
installation secure. When there is an important security issue, we will issue a installation secure. When there is an important security incident, we will issue
[Qubes Security Bulletin (QSB)](/security/qsb/) via the [Qubes Security a [Qubes Security Bulletin (QSB)](/security/qsb/) via the [Qubes Security
Pack (`qubes-secpack`)](/security/pack/). It is very important to read each new Pack (`qubes-secpack`)](/security/pack/). It is very important to read each new
QSB and follow any user instructions it contains. Most of the time, simply QSB and follow any user instructions it contains. Most of the time, simply
updating your system normally, as described below, will be sufficient to obtain updating your system normally, as described below, will be sufficient to obtain
@ -36,7 +36,7 @@ your part, which will be explained in the QSB.
## Checking for updates ## Checking for updates
By default, the Qubes Update tool will appear as an icon in the Notification By default, the **Qubes Update** tool will appear as an icon in the Notification
Area when updates are available. Area when updates are available.
[![Qube Updates Available](/attachment/doc/r4.0-qube-updates-available.png)](/attachment/doc/r4.0-qube-updates-available.png) [![Qube Updates Available](/attachment/doc/r4.0-qube-updates-available.png)](/attachment/doc/r4.0-qube-updates-available.png)
@ -124,8 +124,8 @@ as well as OSes used in [templates](/doc/templates/) (and
**It's very important that you use only supported releases so that you continue **It's very important that you use only supported releases so that you continue
to receive security updates.** This means that you *must* periodically upgrade to receive security updates.** This means that you *must* periodically upgrade
Qubes OS and your templates before they reach EOL. You can always see which Qubes OS and your templates before they reach EOL. You can always see which
versions of Qubes OS and select templates are supported on the [Supported versions of Qubes OS and select templates are supported on the [supported
Versions](/doc/supported-releases/) page. releases](/doc/supported-releases/) page.
In the case of Qubes OS itself, we will make an In the case of Qubes OS itself, we will make an
[announcement](/news/categories/#releases) when a supported Qubes OS release is [announcement](/news/categories/#releases) when a supported Qubes OS release is
@ -141,8 +141,7 @@ set their own
for when each Fedora release reaches EOL. You can always find out when an OS for when each Fedora release reaches EOL. You can always find out when an OS
reaches EOL from the upstream project that maintains it. We also pass along any reaches EOL from the upstream project that maintains it. We also pass along any
EOL notices we receive for official template OSes as a convenience to Qubes EOL notices we receive for official template OSes as a convenience to Qubes
users (see [Supported Versions: users (see [supported template releases](/doc/supported-releases/#templates)).
Templates](/doc/supported-releases/#templates)).
The one exception to all this is the specific release used for dom0 (not to be The one exception to all this is the specific release used for dom0 (not to be
confused with Qubes OS as a whole), which [doesn't have to be confused with Qubes OS as a whole), which [doesn't have to be