From db6333951fc6a39b8d08c8db56cb00d4c6a5f14e Mon Sep 17 00:00:00 2001 From: ejd1967 <86053726+ejd1967@users.noreply.github.com> Date: Thu, 17 Jun 2021 14:08:27 +0300 Subject: [PATCH] Update fedora-upgrade.md --- user/managing-os/fedora/fedora-upgrade.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/user/managing-os/fedora/fedora-upgrade.md b/user/managing-os/fedora/fedora-upgrade.md index 6333e20b..5b0caef1 100644 --- a/user/managing-os/fedora/fedora-upgrade.md +++ b/user/managing-os/fedora/fedora-upgrade.md @@ -128,8 +128,7 @@ The same general procedure may be used to upgrade any template based on the stan In this case, one option is to [resize the TemplateVM's disk image](/doc/resize-disk-image/) before reattempting the upgrade process. (See [Additional Information](#additional-information) below for other options.) -4. Check that you are on the correct (new) Fedora release. - +4. Check that you are on the correct (new) Fedora release. Do this check only after completing the upgrade process (number 3 above). This is NOT a troubleshooting procedure for fixing download issues from the repository. This test verifies that your clone has successfully converted from fedora-old to fedora-new. ``` [user@fedora- ~]$ cat /etc/fedora-release ```