Added a note as a fix to DOCTEAM-1759 (#1964)

Author: sounix000

xml/tuning_multikernel.xml

@@ -28,6 +28,17 @@
    <dm:translation>yes</dm:translation>
   </dm:docmanager>
  <revhistory xml:id="rh-cha-tuning-multikernel">
+   <revision>
+     <date>2026-09-03</date>
+     <revdescription>
+       <para>
+        Kernels selected for removal by <literal>multiversion.kernels</literal>
+        are purged at the next reboot by the <literal>purge-kernels.service</literal>
+        systemd service, which is enabled by default and can also be triggered
+        manually with <literal>zypper purge-kernels</literal>.
+       </para>
+     </revdescription>
+   </revision>
    <revision>
      <date>2026-04-07</date>
      <revdescription>
@@ -226,6 +237,19 @@
      </tip>
     </step>
    </procedure>
+   <note>
+    <title>When the purge is applied</title>
+    <para>
+     Kernels selected for removal are not deleted immediately. They are
+     purged the next time the system boots, by the
+     <systemitem class="service">purge-kernels.service</systemitem> systemd
+     service, which is enabled by default. To apply the purge without
+     rebooting, run <command>zypper purge-kernels</command> as &rootuser;.
+     Add the <option>--dry-run</option> option to preview which kernels
+     would be removed without deleting anything, or
+     <option>--details</option> for a detailed installation summary.
+    </para>
+   </note>
   </sect2>
   <sect2 xml:id="sec-tuning-multikernel-deleteoldkernel">
    <title>Use case: deleting an old kernel after reboot only</title>