-\fB@IMAGEX_PROGNAME@ capture\fR and \fB@IMAGEX_PROGNAME@ append\fR support
-options to optimize incremental backups and to create "delta" WIM files.
-.IP \[bu]
-wimlib (and \fB@IMAGEX_PROGNAME@\fR via \fB@IMAGEX_PROGNAME@ capture\fR)
-supports combining multiple separate directories and files together in a
-configurable way to create a WIM image.
-.IP \[bu]
-Microsoft's ImageX has some weird limitations, like it won't let you extract a
-WIM on a shared folder, and it requires some commands to be run only from
-Windows PE and not from regular Windows. \fB@IMAGEX_PROGNAME@\fR does not have
-these unusual limitations.
-.IP \[bu]
-There are bugs in Microsoft's WIM library and I obviously have not included the
-same bugs in wimlib, although in some cases I have had to work around bugs for
-compatibility purposes.
-.IP \[bu]
-wimlib (and \fB@IMAGEX_PROGNAME@\fR via \fB@IMAGEX_PROGNAME@ mount\fR) support
-mounting an image from a split WIM, but Microsoft's software does not. (Note:
-this functionality is not available in Windows builds of wimlib and
-\fB@IMAGEX_PROGNAME@\fR.)
+On UNIX-like systems, support for saving and restoring UNIX uids (user IDs),
+gids (group IDs), and modes to/from WIM images. This is a wimlib extension, but
+the Microsoft implementation ignores this extra metadata.
+.IP \[bu]
+Multithreaded compression. By default, data compression is multithreaded and
+will use all available processors. In most cases, this can be changed by the
+\fB--threads\fR option.
+.IP \[bu]
+XPRESS, LZX, and LZMS decompression and compression. wimlib contains
+independent implementations of all these compression algorithms. Sometimes they
+can do better than the equivalent Microsoft implementations.
+.IP \[bu]
+"ESD file" support. As mentioned in \fBBACKGROUND INFORMATION\fR, "ESD files"
+use a new WIM format that features solid blocks and LZMS compression. This
+support was first present in wimlib v1.6.0, but v1.7.0 and later have improved
+compatibility.
+.IP \[bu]
+Mounting WIM images. This relies on FUSE (Filesystem in UserSpacE) and is only
+supported on compatible UNIX-like systems, in particular Linux. FreeBSD may
+work but is untested.
+.IP \[bu]
+Split WIMs. A split WIM is a WIM archive split into multiple parts.
+\fB@IMAGEX_PROGNAME@ split\fR can create a split WIM from a standalone WIM, and
+\fB@IMAGEX_PROGNAME@ join\fR can create a standalone WIM from a split WIM.
+.IP \[bu]
+Delta WIMs. A delta WIM contains image metadata but excludes file data already
+present in another WIM file. A delta WIM can be created using
+\fB@IMAGEX_PROGNAME@ capture\fR with the \fB--delta-from\fR option.
+.IP \[bu]
+WIMBoot support. On Windows 8.1 and later, files on an NTFS volume can be
+externally backed by a WIM archive with the help of Microsoft's Windows Overlay
+FileSystem Filter Driver (WOF). With the \fB--wimboot\fR flag,
+\fB@IMAGEX_PROGNAME@ apply\fR will extract "pointer files" (actually NTFS
+reparse points handled by the WOF driver) to the WIM archive rather than the
+files themselves.
+.IP \[bu]
+Fast incremental backups. Using the \fB--update-of\fR option of
+\fB@IMAGEX_PROGNAME@ capture\fR or \fB@IMAGEX_PROGNAME@ append\fR, you can
+optimize an image capture so that files that are unmodified based on timestamps
+are not be read from disk. But even without this option, since the WIM format
+features single-instance files, a file identical to any already present in the
+WIM archive (in any image) will not be written, but rather a reference to the
+stored file will be used.