repo refresh before transactional-update (#3576) (#3588)

* repo refresh before transactional-update
#3573
SUSE/spacewalk#26156
* run `zypper ref` plus cosmetic fixes

CHANGELOG.md

@@ -6,6 +6,8 @@
   references in Installation and Upgrade Guide
 - Updated Troubleshooting Autoinstallation in Administration Guide
 - Added support for SUSE Linux Micro 6.1
+- Added step to refresh repository before calling transactional-update
+  in Installation and Upgrade Guide
 - Added external link for creating virtual network peer for Azure in
   Specialized Gudes (bsc#1234441)
 - Clarified SSH authentication methods during Web UI bootstrap process in

modules/installation-and-upgrade/pages/container-management/updating-server-containers.adoc

@@ -2,13 +2,17 @@
 
 Before running the upgrade command, it is recommended to upgrade the [literal]``mgradm`` tool first.
 
-.Procedure
-. One can do so by running the following command:
+.Procedure: Upgrading Server
+. Refresh software repository with [command]``zypper``:
++
+----
+zypper ref
+----
+. Apply available updates with [command]``transactional-update``:
 +
 ----
 transactional-update
 ----
-
 . If updates were applied, [literal]``reboot``.
 
 . The {productname} Server container can be updated using the following command:
@@ -17,9 +21,12 @@ transactional-update
 ----
 mgradm upgrade podman
 ----
++
 
 This command will bring the status of the container up-to-date and restart the server.
 
+
+
 .Upgrading to specific version
 [NOTE]
 ====