diff --git a/docs/management/updates.md b/docs/management/updates.md
index e998a468..d548d326 100644
--- a/docs/management/updates.md
+++ b/docs/management/updates.md
@@ -136,8 +136,15 @@ Also known as RPU, **this is the advised way to update your pool**. By just clic
 This powerful and fully automated mechanism requires some prerequisites: all your VMs disks must be on a one (or more) shared storage. Also, high-availability will be automatically disabled, as the XO load balancer plugin and backup jobs. Everything will be enabled back when it's done!
 :::
 
+**XCP-ng 8.3**
+
+Starting with XCP-ng 8.3, Rolling Pool Updates (RPUs) now handle pools that utilize XOSTOR. If there is no LINSTOR Storage Repository (SR), the RPU proceeds as usual. However, if a LINSTOR SR is present, the update process includes additional steps to ensure compatibility before performing the standard rolling update.
+
+**XCP-ng 8.2**
+
 :::warning
-RPU is disabled for pools with XOSTOR SRs. The reason is that after a reboot of a just updated host, it's possible that it can no longer communicate with other hosts through LINSTOR satellites. In fact LINSTOR expects that we always use satellites and controllers with the same version.
+
+On XCP-ng 8.2, RPU is disabled for pools with XOSTOR SRs. The reason is that after a reboot of a just updated host, it's possible that it can no longer communicate with other hosts through LINSTOR satellites. In fact LINSTOR expects that we always use satellites and controllers with the same version.
 
 To avoid problems, it is strongly recommended to update the satellites, controllers packages of each host without rebooting:
 ```