@@ -3,9 +3,9 @@
 [![CI](https://github.com/rpPH4kQocMjkm2Ve/atomic-upgrade/actions/workflows/ci.yml/badge.svg)](https://github.com/rpPH4kQocMjkm2Ve/atomic-upgrade/actions/workflows/ci.yml)
 ![License](https://img.shields.io/github/license/rpPH4kQocMjkm2Ve/atomic-upgrade)
 
-Atomic system upgrades for Arch Linux on Btrfs + UKI + Secure Boot.
+Atomic system upgrades for Arch Linux on Btrfs + UKI + optional Secure Boot.
 
-NixOS/Silverblue-style generational updates on plain Arch: Btrfs snapshot → chroot → upgrade → build UKI → sign → reboot. Rollback is selecting a previous entry in systemd-boot.
+NixOS/Silverblue-style generational updates on plain Arch: Btrfs snapshot → chroot → upgrade → build UKI → sign → reboot. Rollback is selecting a previous UKI entry in the boot menu.
 
 ## How it works
 
@@ -23,7 +23,9 @@ sudo atomic-upgrade
   reboot → new generation active
 ```
 
-Rollback: select a previous UKI entry in systemd-boot at boot time.
+Rollback: select a previous UKI entry in the boot menu.
+
+Each generation is a snapshot + UKI pair. The UKI contains the kernel and initramfs from that snapshot, and its cmdline points to that specific subvolume. Rollback works because each boot menu entry maps to one complete system state.
 
 ## Comparison
 
@@ -35,7 +37,7 @@ Rollback: select a previous UKI entry in systemd-boot at boot time.
 |---------|---------------|---------------------|------------------------|-------|---------------|
 | **Base distro** | Arch | Any (openSUSE native) | Any Btrfs | NixOS | Fedora |
 | **Atomic upgrades** | ✓ (chroot) | ✗ (pre/post snapshots) | ✗ (pre/post snapshots) | ✓ | ✓ |
-| **Rollback** | Boot menu (systemd-boot) | Boot menu (GRUB) | Boot menu (GRUB) | Boot menu | Boot menu (GRUB) |
+| **Rollback** | Boot menu (UKI) | Boot menu (GRUB) | Boot menu (GRUB) | Boot menu | Boot menu (GRUB) |
 | **Secure Boot** | ✓ (sbctl, optional) | Via separate setup | Via separate setup | ✓ (lanzaboote) | ✓ |
 | **UKI per generation** | ✓ | ✗ | ✗ | Optional | Optional |
 | **Upgrade isolation** | Chroot snapshot | None (live) | None (live) | Nix build | OSTree |
@@ -293,11 +295,12 @@ On disks larger than ~200 GB, the free percentage may drop below 10% while absol
 
 ### Prerequisites
 
-- Btrfs root filesystem
-- systemd-boot
-- Root on a Btrfs subvolume (any name — snapshots are created as `root-<timestamp>`)
+- Btrfs root filesystem on a subvolume (any name — snapshots are created as `root-<timestamp>`)
+- A bootloader or UEFI firmware that discovers UKI files (Type #2 entries) — systemd-boot, rEFInd, direct UEFI boot, etc.
 - Secure Boot with sbctl *(optional, enable with `SBCTL_SIGN=1`)*
 
+The tool places `.efi` files into `ESP/EFI/Linux/` (signed or unsigned depending on `SBCTL_SIGN`). Any boot environment that picks up UKI files from that path will work.
+
 > **Important:** `/home`, `/var/log`, `/var/cache`, and other stateful data
 > should live on **separate Btrfs subvolumes**. Only the root subvolume is
 > snapshotted and rolled back — anything on the same subvolume will be
 
@@ -1,6 +1,9 @@
 .\" Automatically generated by Pandoc 3.5
 .\"
-.TH "ATOMIC\-UPGRADE" "8" "" "atomic\-upgrade" "System Administration"
+.TH "" "" "" ""
+.SS \[ga]\[ga]\[ga]markdown
+title: ATOMIC\-UPGRADE section: 8 header: System Administration footer:
+atomic\-upgrade \[em]
 .SH NAME
 atomic\-upgrade \[em] atomic system upgrades for Arch Linux on Btrfs
 .SH SYNOPSIS
@@ -17,9 +20,17 @@ subvolume, mounts it, runs a command inside an arch\-chroot (default:
 Kernel Image (UKI), optionally signs it with \f[B]sbctl\f[R](8), and
 runs garbage collection.
 .PP
+Each generation is a snapshot + UKI pair.
+The UKI contains the kernel and initramfs from that snapshot, and its
+cmdline points to that specific subvolume.
+Rollback works because each boot menu entry maps to one complete system
+state.
+.PP
 The new generation becomes active on next reboot.
-Rollback is performed by selecting a previous UKI entry in
-systemd\-boot.
+Rollback is performed by selecting a previous UKI entry in the boot
+menu.
+Any bootloader or UEFI firmware that discovers Type #2 entries works
+\[em] systemd\-boot, rEFInd, direct UEFI boot, etc.
 .PP
 \f[B]atomic\-rebuild\-uki\f[R] rebuilds the UKI for an existing
 generation subvolume.
@@ -179,5 +190,4 @@ sudo atomic\-rebuild\-uki \-\-list
 .SH SEE ALSO
 \f[B]atomic\-gc\f[R](8), \f[B]atomic.conf\f[R](5),
 \f[B]btrfs\-subvolume\f[R](8), \f[B]ukify\f[R](1), \f[B]sbctl\f[R](8),
-\f[B]pacman\f[R](8), \f[B]arch\-chroot\f[R](8),
-\f[B]systemd\-boot\f[R](7)
+\f[B]pacman\f[R](8), \f[B]arch\-chroot\f[R](8)
@@ -1,3 +1,4 @@
+```markdown
 ---
 title: ATOMIC-UPGRADE
 section: 8
@@ -22,8 +23,15 @@ mounts it, runs a command inside an arch-chroot (default: **pacman -Syu**),
 updates *fstab*, builds a Unified Kernel Image (UKI), optionally signs it
 with **sbctl**(8), and runs garbage collection.
 
+Each generation is a snapshot + UKI pair. The UKI contains the kernel and
+initramfs from that snapshot, and its cmdline points to that specific
+subvolume. Rollback works because each boot menu entry maps to one complete
+system state.
+
 The new generation becomes active on next reboot. Rollback is performed by
-selecting a previous UKI entry in systemd-boot.
+selecting a previous UKI entry in the boot menu. Any bootloader or UEFI
+firmware that discovers Type #2 entries works — systemd-boot, rEFInd,
+direct UEFI boot, etc.
 
 **atomic-rebuild-uki** rebuilds the UKI for an existing generation subvolume.
 Use it to recover an accidentally deleted *.efi* file.
@@ -164,4 +172,4 @@ List subvolumes and UKI status:
 # SEE ALSO
 
 **atomic-gc**(8), **atomic.conf**(5), **btrfs-subvolume**(8), **ukify**(1),
-**sbctl**(8), **pacman**(8), **arch-chroot**(8), **systemd-boot**(7)
+**sbctl**(8), **pacman**(8), **arch-chroot**(8)