atomic-desktops/docs
10
4
Fork 8
Code Issues 4 Pull requests 1 Activity

Merge pull request 'Fix grammar and typo' (#15) from jonnyse/docs:fixes into main

Browse source 
Reviewed-on: #15
Reviewed-by: Hristo Marinov <hricky@noreply.forge.fedoraproject.org>
This commit is contained in:
Hristo Marinov 2026-02-01 17:32:00 +00:00
commit df76cd8243
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
modules/ROOT/pages/updates-upgrades-rollbacks.adoc
View file

@ -83,7 +83,7 @@ For example, if you are currently using Silverblue, you can switch to Kinoite.
Fedora Kinoite is similar to Fedora Silverblue, except for the fact that it uses the KDE Plasma desktop instead of the GNOME desktop.
What this means is, you can rebase to Fedora Kinoite to try it out, without ever touching your current system.
Because the two system images are isolated from eachother, the two desktop environments will never be installed at the same time.
Because the two system images are isolated from each other, the two desktop environments will never be installed at the same time.
All your flatpak apps and files in the `/home` directory will remain persistent between rebases.
Same applies for testing out the development version of Fedora Atomic Desktops, which is Rawhide.
@ -105,7 +105,7 @@ There are two ways to roll back to the previous version:
. Permanent rollbacks: to permanently switch back to the previous deployment, use the `rpm-ostree rollback` command.
After rolling back, you will technically be on an old OS version, and may be prompted to update.
Updating will undo the rollback, so should be avoided if you want the rollback to stay in effect.
Updating will undo the rollback, so it should be avoided if you want the rollback to stay in effect.
`rpm-ostree` only keeps one rollback version available by default.
If you want to rollback to another version than the one currently available on your system, you can do so with the following commands:
@ -137,7 +137,7 @@ NOTE: This will deploy the exact version as requested and will not include overl
[[pinning-and-cleaning-deployments]]
== Pinning and cleaning deployments
By default, the `rpm-ostree upgrade` or `pm-ostree rebase` commands will keep at most two bootable deployments, though the underlying technology supports more.
By default, the `rpm-ostree upgrade` or `rpm-ostree rebase` commands will keep at most two bootable deployments, though the underlying technology supports more.
In some cases, such as a major version upgrade or rebase, you may want to keep your current deployment as a guaranteed fallback.
OSTree allows you to pin deployments.
Pinning ensures that your deployment of choice is kept and not discarded.