diff --git a/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md b/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md
index 8222c4d4d..397bd9dfc 100644
--- a/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md
+++ b/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md
@@ -99,30 +99,30 @@ Verify that required traffic is allowed. Check the [Networking prerequisites](ec
 
     * For Podman 5
 
-        * Install version `5.2.2-13.*` using dnf.
+        * Install version `5.2.2-*` (latest version of Podman 5.2.2) using dnf.
 
             :::{note}
-            As mentioned in [Migrating to Podman 5](migrate-to-podman-5.md) it is recommended to install Podman `5.2.2-13` since this is the latest supported version.
+            As mentioned in [Migrating to Podman 5](migrate-to-podman-5.md) it is recommended to install Podman `5.2.2-*` since this is the latest supported version.
 
-            If you decide to install a previous Podman 5 version, make sure to replace `5.2.2-13` with the desired version in the commands below.
+            If you decide to install a previous Podman 5 version, make sure to replace `5.2.2-*` with the desired version in the commands below.
 
             The version lock is still required for previous versions, to prevent automatic in-place updates that may be affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473).
             :::
 
             ```sh
-            sudo dnf install podman-5.2.2-13.* podman-remote-5.2.2-13.*
+            sudo dnf install podman-5.2.2-* podman-remote-5.2.2-*
             ```
-        * To prevent automatic Podman updates to unsupported versions, configure the Podman version to be locked at version `5.2.2-13.*`.
+        * To prevent automatic Podman updates to unsupported versions, configure the Podman version to be locked at version `5.2.2-*`.
 
             ```sh
             ## Install versionlock
             sudo dnf install 'dnf-command(versionlock)'
 
             ## Lock major version
-            sudo dnf versionlock add --raw 'podman-5.2.2-13.*'
-            sudo dnf versionlock add --raw 'podman-remote-5.2.2-13.*'
+            sudo dnf versionlock add --raw 'podman-5.2.2-*'
+            sudo dnf versionlock add --raw 'podman-remote-5.2.2-*'
 
-            ## Verify that podman-5.2.2-13.* and podman-remote-5.2.2-13.* appear in the output
+            ## Verify that podman-5.2.2-* and podman-remote-5.2.2-* appear in the output
             sudo dnf versionlock list
             ```
 
diff --git a/deploy-manage/deploy/cloud-enterprise/migrate-to-podman-5.md b/deploy-manage/deploy/cloud-enterprise/migrate-to-podman-5.md
index 1eb8a3364..27f2ddcb9 100644
--- a/deploy-manage/deploy/cloud-enterprise/migrate-to-podman-5.md
+++ b/deploy-manage/deploy/cloud-enterprise/migrate-to-podman-5.md
@@ -7,7 +7,7 @@ applies_to:
 
 Following are the supported upgrade paths for Podman 5 in {{ece}}.
 
-| **From ↓** ...       **To →**           | Podman 5.2.2-9 | Podman 5.2.2-11 | Podman 5.2.2-13 | Podman 5.2.3 |
+| **From ↓** ...       **To →**           | Podman 5.2.2-9 | Podman 5.2.2-11 | Podman 5.2.2-latest | Podman 5.2.3 |
 |-----------------------------------------|----------------|-----------------|-----------------|--------------|
 | **<vanilla Linux installation> (grow)** | ✓ ^*^          | ✓ ^*^           | ✓               | X            |
 | **Docker (grow-and-shrink)**            | ✓ ^*^          | ✓ ^*^           | ✓               | X            |
@@ -18,11 +18,11 @@ Following are the supported upgrade paths for Podman 5 in {{ece}}.
 
 
 
-^*^ *Supported but not recommended given that a newer version (Podman `5.2.2-13`) is available.*
+^*^ *Supported but not recommended given that a newer version (latest version of Podman `5.2.2`) is available.*
 
-Podman `5.2.2-13` is only supported when conducting a **fresh {{ece}} installation** or performing a **grow-and-shrink update** from Docker or Podman 4.
+The latest version of Podman `5.2.2` is only supported when conducting a **fresh {{ece}} installation** or performing a **grow-and-shrink update** from Docker or Podman 4.
 
-For **in-place updates**, it is recommended to use Podman `5.2.2-9`, since upgrades to versions `5.2.2-11` and `5.2.2-13` are affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473).
+For **in-place updates**, it is recommended to use Podman `5.2.2-9`, since upgrades to versions `5.2.2-11` and latest version of `5.2.2` are affected by a known [memory leak issue](https://github.com/containers/podman/issues/25473).
 When performing an in-place update, make sure to configure the Podman version to be locked at version `5.2.2-9.*`, by following the instructions below.
 
 ```sh