Update wimlib-imagex man pages, especially the main one

diff --git a/doc/man1/imagex-apply.1.in b/doc/man1/imagex-apply.1.in
index 93a82e0dae8f9c16e6de264ca8e740f066295ac9..8d3f72a867786c64f264e0787a2ff8f64c4f7aa0 100644 (file)
--- a/doc/man1/imagex-apply.1.in
+++ b/doc/man1/imagex-apply.1.in
@@ -441,7 +441,7 @@ wimlib cannot extract such files until they are first decrypted.
 .PP
 \fIDirectory traversal attacks\fR:  wimlib validates filenames before extracting
 them and is not vulnerable to directory traversal attacks.  This is in contrast
-to Microsoft WIMGAPI/Imagex/Dism which can overwrite arbitrary files on the
+to Microsoft WIMGAPI/ImageX/DISM which can overwrite arbitrary files on the
 target drive when extracting a malicious WIM file containing files named
 \fI..\fR or containing path separators.
 .SH EXAMPLES

diff --git a/doc/man1/imagex-capture.1.in b/doc/man1/imagex-capture.1.in
index f81118ff532dd5b92590ef17a296c89707675aed..9f1e6a68e38db5f4dc72fc36d8316278142610ad 100644 (file)
--- a/doc/man1/imagex-capture.1.in
+++ b/doc/man1/imagex-capture.1.in
@@ -127,7 +127,7 @@ subject to the WIM format's compression.)
 .SH DIRECTORY CAPTURE (WINDOWS)
 On Windows, \fB@IMAGEX_PROGNAME@ capture\fR and \fB@IMAGEX_PROGNAME@ append\fR
 natively support Windows-specific and NTFS-specific data.  They therefore act
-similarly to the corresponding commands of Microsoft's ImageX.  For best
+similarly to the corresponding commands of Microsoft's ImageX or DISM.  For best
 results, the directory being captured should be on an NTFS volume and
 \fB@IMAGEX_PROGNAME@\fR should be run with Administrator privileges; however,
 non-NTFS filesystems and running without Administrator privileges are also
@@ -207,8 +207,8 @@ and "LZX", instead of "fast" and "maximum", respectively.
 .IP ""
 As of wimlib v1.6.0, a third compression type, "recovery" or "LZMS", is also
 available.  Its use is generally not recommended because other than wimlib
-itself, as of Windows 8 it is only compatible with WIMGAPI and Windows Setup
-(not even ImageX or Dism).  However, LZMS is the compression algorithm used in
+itself, it is only compatible with WIMGAPI Windows 8 and later, and DISM Windows
+8.1 and later.  However, LZMS is the compression algorithm used by default in
 packed resources created if the \fB--pack-streams\fR option is specified.
 .TP
 \fB--compress-slow\fR
@@ -240,8 +240,8 @@ together, rather than each unique stream ("file") independently.  This can
 result in a significantly better compression ratio, but this format greatly
 decreases the performance of random access to the data, as may occur on a WIM
 mounted with \fB@IMAGEX_PROGNAME@ mount\fR.  Also, WIMs created using this
-option use a different version number in their header and as of Windows 8 are
-only compatible with Windows Setup and WIMGAPI, not even ImageX and Dism.
+option use a different version number in their header and are only compatible
+with WIMGAPI Windows 8 and later, and DISM Windows 8.1 and later.
 .IP ""
 The default compression type and chunk size in packed resources is LZMS with
 2^25 (33554432) byte chunks.  This is independent of the WIM's main compression
@@ -538,8 +538,8 @@ modified.
 .IP ""
 Note: unlike "pipable" WIMs (created with the \fB--pipable\fR option), "delta"
 WIMs (created with the \fB--delta-from\fR option) are compatible with
-Microsoft's software.  You can use the /ref option of imagex.exe to reference
-the base WIM(s), similar to above.
+Microsoft's software.  For example, you can use the /ref option of ImageX to
+reference the base WIM(s), similar to above.
 .IP ""
 Additional note:  \fB@IMAGEX_PROGNAME@\fR is generalized enough that you can in
 fact combine \fB--pipable\fR and \fB--delta-from\fR to create pipable delta
@@ -567,7 +567,7 @@ fully rebuilt (e.g. with \fB--rebuild\fR), in which case you should delete the
 temporary file left over.
 .PP
 \fB@IMAGEX_PROGNAME@\fR creates WIMs compatible with Microsoft's software
-(imagex.exe, Dism.exe, wimgapi.dll), with some caveats:
+(WIMGAPI, ImageX, DISM), with some caveats:
 .IP \[bu] 4
 With \fB@IMAGEX_PROGNAME@\fR on UNIX-like systems, it is possible to create a
 WIM image containing files with names differing only in case, or files with
@@ -589,9 +589,8 @@ the \fB--pipable\fR flag was specified.
 WIMs captured with a non-default chunk size (with the \fB--chunk-size\fR option)
 or as solid archives (with the \fB--pack-streams\fR option) or with LZMS
 compression (with \fB--compress\fR=LZMS or \fB--compress\fR=recovery) have
-varying levels of compatibility with Microsoft's software.  The best
-compatibility is achieved with WIMGAPI itself (not ImageX or Dism) on Windows 8
-or later.
+varying levels of compatibility with Microsoft's software.  Generally, more
+recent versions of Microsoft's software are more compatible.
 .SH EXAMPLES
 First example:  Create a new WIM 'mywim.wim' with "maximum" (LZX) compression
 that will contain a captured image of the directory tree 'somedir'.  Note that

diff --git a/doc/man1/imagex-delete.1.in b/doc/man1/imagex-delete.1.in
index 1726387d423ca03686618521cf16210008c4e202..25c0008eab48db88c976d2fe1acd3ba7b5903d99 100644 (file)
--- a/doc/man1/imagex-delete.1.in
+++ b/doc/man1/imagex-delete.1.in
@@ -16,12 +16,12 @@ keyword "all" to indicate that all images are to be deleted.  Use the
 contains.
 .SH NOTES
 By default, the WIM file is rebuilt with all unnecessary file data removed.
-This is different from Microsoft's imagex.exe, which only will delete the
+This is different from Microsoft's ImageX and DISM, which only will delete the
 directory tree metadata and XML data for this operation.  (See the \fB--soft\fR
 option for the other kind of delete).
 .PP
-Also, unlike Microsoft's imagex.exe, it is legal to delete all the images from a
-WIM and have a WIM with 0 images, although such a file wouldn't be very useful.
+Also wimlib allows you to delete all the images from a WIM and have a WIM with 0
+images, although such a file wouldn't be very useful.
 .PP
 \fB@IMAGEX_PROGNAME@ delete\fR does not support split WIMs.
 .SH OPTIONS

diff --git a/doc/man1/imagex-split.1.in b/doc/man1/imagex-split.1.in
index 529fc598cfe255ff3379639bc00e8a33b6446e55..b425f91cc2c4bcff430e6acd5f17c46cb4345f9c 100644 (file)
--- a/doc/man1/imagex-split.1.in
+++ b/doc/man1/imagex-split.1.in
@@ -27,7 +27,7 @@ etc. where each part is at most 100 MiB:
 .RE
 .SH LIMITATIONS
 It it possible for the size of the parts to exceed the \fIPART_SIZE\fR given.
-This is impossible to avoid and Microsoft's program has this problem as well
+This is impossible to avoid
 because the WIM file format provides no way to divide a single file resource in
 the WIM among multiple split WIM parts.  So if you, for example, have a file
 inside the WIM that is 100 MiB, then an uncompressed split WIM will have at

diff --git a/doc/man1/imagex.1.in b/doc/man1/imagex.1.in
index 031259c06e63a8fa60bc71e7f2a674450e449e33..e395ad6b739bc03beab55fa00820af0215f45328 100644 (file)
--- a/doc/man1/imagex.1.in
+++ b/doc/man1/imagex.1.in
@@ -1,6 +1,6 @@
 .TH WIMLIB-IMAGEX 1 "May 2014" "@IMAGEX_PROGNAME@ @VERSION@" "User Commands"
 .SH NAME
-@IMAGEX_PROGNAME@ \- Create, modify, extract, mount, or unmount a WIM (Windows Imaging Format) archive
+@IMAGEX_PROGNAME@ \- Extract, create, modify, or mount a WIM (Windows Imaging Format) archive
 .SH SYNOPSIS
 \fB@IMAGEX_PROGNAME@ append\fR \fIarguments...\fR
 .br
@@ -32,17 +32,30 @@
 .br
 \fB@IMAGEX_PROGNAME@ update\fR \fIarguments...\fR
 .SH DESCRIPTION
-\fB@IMAGEX_PROGNAME@\fR deals with archives in the Windows Imaging Format (.wim
-files). Its interface is meant to be similar to Microsoft's "imagex.exe"
-program, but it also provide many useful extensions.
+\fB@IMAGEX_PROGNAME@\fR deals with archives in the Windows Imaging Format (WIM).
+Its interface is similar to Microsoft's ImageX, but \fB@IMAGEX_PROGNAME@\fR is
+cross-platform and has useful improvements and extensions.
 .PP
-To do its work, \fB@IMAGEX_PROGNAME@\fR uses \fBwimlib\fR, a C library which
-provides interfaces for manipulating WIM archives.  You can wimlib in your own
-programs if desired, although \fB@IMAGEX_PROGNAME@\fR already provides access to
-most of wimlib's functionality.  In some cases, however, there are general
-interfaces which are only used by \fB@IMAGEX_PROGNAME@\fR in a specific way, so
-it may be worth taking a look if you're looking to do something beyond what
-\fB@IMAGEX_PROGNAME@\fR directly supports.
+To do its work, \fB@IMAGEX_PROGNAME@\fR uses \fBwimlib\fR, an open source C
+library that provides interfaces for manipulating WIM archives.  wimlib is
+completely independent from the equivalent Microsoft implementation (WIMGAPI, or
+wimgapi.dll).  You can use wimlib in your own programs, although for
+command-line use \fB@IMAGEX_PROGNAME@\fR already provides access to most of
+wimlib's functionality.
+.SH BACKGROUND INFORMATION
+The Windows Imaging Format (WIM) was designed by Microsoft primarily for
+archiving Windows filesystems, such as NTFS.  However, it can be used on other
+platforms as well, with some limitations.  A WIM archive contains one or more
+images, each of which is a logically independent directory tree.  Images are
+indexed starting from 1, and each may also have a name.  File data is stored as
+content-addressable "streams" that are deduplicated across the entire archive.
+Streams may be compressed using one of several compression algorithms, including
+XPRESS and LZX.
+.PP
+An update of the WIM format released with Windows 8 features solid compression
+using the LZMS compression algorithm.  Such files are also called "ESD files"
+and may carry the extension \.esd instead of .wim.  \fB@IMAGEX_PROGNAME@\fR
+v1.6.0 and later supports these new files, unless they are encrypted.
 .SH COMMANDS
 \fB@IMAGEX_PROGNAME@\fR accepts one of a number of commands (listed above in
 \fBSYNOPSYS\fR), and additional arguments depending on the specific command.
@@ -54,132 +67,142 @@ Note: to save typing, if appropriate hard links or batch files have been
 installed, a command \fB@IMAGEX_PROGNAME@ \fICOMMAND\fR can also be accessed as
 simply \fBwim\fICOMMAND\fR; for example, \fBwimapply\fR for \fB@IMAGEX_PROGNAME@
 apply\fR.
-.SH SUPPORTED FEATURES
-The following are some of the main features currently supported by
-\fB@IMAGEX_PROGNAME@\fR, and pointers to the relevant commands:
+.SH GENERAL FEATURES
+The following are some of the general features, or use cases, currently
+supported by \fB@IMAGEX_PROGNAME@\fR, and pointers to the relevant commands:
 .IP \[bu] 4
-Create a standalone WIM from a directory or NTFS volume (\fB@IMAGEX_PROGNAME@ capture\fR)
-.IP \[bu]
-Capture a WIM image directly to standard output in a special pipable format
-(\fB@IMAGEX_PROGNAME@ capture\fR)
-.IP \[bu]
-Append a directory or NTFS volume onto a standalone WIM as a new image (\fB@IMAGEX_PROGNAME@
-append\fR)
+Display information about a WIM file
+ (\fB@IMAGEX_PROGNAME@ info\fR)
 .IP \[bu]
-Apply an image from a standalone or split WIM to a directory or NTFS volume
-(\fB@IMAGEX_PROGNAME@ apply\fR)
+List the files in a WIM image
+ (\fB@IMAGEX_PROGNAME@ dir\fR)
 .IP \[bu]
-Apply an image from a special pipable WIM format sent over standard input
-(\fB@IMAGEX_PROGNAME@ apply\fR)
+Extract, or "apply", a full WIM image
+ (\fB@IMAGEX_PROGNAME@ apply\fR)
 .IP \[bu]
-Mount an image from a standalone or split WIM read-only (\fB@IMAGEX_PROGNAME@
-mount\fR) (not available on Windows)
-.IP \[bu]
-Mount an image from a standalone WIM read-write (\fB@IMAGEX_PROGNAME@
-mountrw\fR) (not available on Windows)
-.IP \[bu]
-Extract individual files or directories from a WIM without mounting it
-(\fB@IMAGEX_PROGNAME@ extract\fR)
+Extract files or directories from a WIM image
+ (\fB@IMAGEX_PROGNAME@ extract\fR)
+.IP \[bu] 4
+Capture a WIM image and save it to a new WIM file
+ (\fB@IMAGEX_PROGNAME@ capture\fR)
 .IP \[bu]
-Make changes to a WIM image without mounting it (\fB@IMAGEX_PROGNAME@ update\fR)
+Capture a WIM image and append it to an existing WIM file
+ (\fB@IMAGEX_PROGNAME@ append\fR)
 .IP \[bu]
-Delete image(s) from a standalone WIM (\fB@IMAGEX_PROGNAME@ delete\fR)
+Modify a WIM image by adding, deleting, or renaming files
+ (\fB@IMAGEX_PROGNAME@ update\fR)
 .IP \[bu]
-Export image(s) from a standalone or split WIM (\fB@IMAGEX_PROGNAME@ export\fR)
+(Linux only) Mount a WIM image read-only
+ (\fB@IMAGEX_PROGNAME@ mount\fR)
 .IP \[bu]
-Display information about a WIM file (\fB@IMAGEX_PROGNAME@ info\fR, \fB@IMAGEX_PROGNAME@ dir\fR)
+(Linux only) Mount a WIM image read-write
+ (\fB@IMAGEX_PROGNAME@ mountrw\fR)
 .IP \[bu]
-Change the name or description of an image in the WIM (\fB@IMAGEX_PROGNAME@ info\fR)
+Delete an image from a WIM file
+ (\fB@IMAGEX_PROGNAME@ delete\fR)
 .IP \[bu]
-Change which image in a WIM is bootable (\fB@IMAGEX_PROGNAME@ info\fR)
+Export image(s) from a WIM file
+ (\fB@IMAGEX_PROGNAME@ export\fR)
 .IP \[bu]
-Combine split WIMs into one standalone WIM (\fB@IMAGEX_PROGNAME@ join\fR)
+Change the name or description of a WIM image
+ (\fB@IMAGEX_PROGNAME@ info\fR)
 .IP \[bu]
-Split a standalone WIM into multiple parts (\fB@IMAGEX_PROGNAME@ split\fR)
+Change the bootable image index of a WIM file
+ (\fB@IMAGEX_PROGNAME@ info\fR)
 .IP \[bu]
-Easily remove wasted space in a WIM file and optionally recompress it (\fB
-@IMAGEX_PROGNAME@ optimize\fR)
+Rebuild, and optionally recompress, a WIM file
+ (\fB@IMAGEX_PROGNAME@ optimize\fR)
 .IP \[bu]
-Support for all WIM compression types, both compression and decompression
-(XPRESS, LZX, LZMS, and None).
+Split a WIM file into multiple parts
+ (\fB@IMAGEX_PROGNAME@ split\fR)
 .IP \[bu]
-WIM integrity table is supported (\fB--check\fR option to many commands)
-.SH DIFFERENCES FROM MICROSOFT IMAGEX
-Although \fB@IMAGEX_PROGNAME@\fR shares some similarities with Microsoft's
-implementation of ImageX, this section lists some of the many noteworthy
-differences between the two programs:
+Join a split WIM
+ (\fB@IMAGEX_PROGNAME@ join\fR)
+.SH DETAILED FEATURES
+This section presents some of the interesting features of
+\fB@IMAGEX_PROGNAME@\fR in more detail.
 .IP \[bu] 4
-\fB@IMAGEX_PROGNAME@\fR is supported on both UNIX-like systems and Windows;
-thus, some functionality was designed around this.
-.IP \[bu]
-The command-line syntax of the two programs is similar but not exactly the same.
-.IP \[bu]
-Because Microsoft designed the WIM file format to accomodate Windows-specific
-and NTFS-specific features, on UNIX-like systems wimlib must have two separate
-image capture and application modes (although the \fB@IMAGEX_PROGNAME@\fR
-commands for the modes are the same): one for image capture and application
-from/to a directory, and one for the capture or application of an image
-specifically from/to an NTFS volume.
-.IP ""
-Note: the above applies to builds of \fB@IMAGEX_PROGNAME@\fR for UNIX-like
-systems.  On the Windows build, there is only one image capture and application
-mode, similar to Microsoft's ImageX.
-.IP \[bu]
-wimlib supports multithreaded compression, which can make it much faster to
-create compressed WIM files.
-.IP \[bu]
-\fB@IMAGEX_PROGNAME@\fR offers the extra commands \fB@IMAGEX_PROGNAME@
-extract\fR and \fB@IMAGEX_PROGNAME@ update\fR, which let you quickly extract
-files from or make changes to a WIM image without mounting it.
-.IP \[bu]
-\fB@IMAGEX_PROGNAME@\fR offers the extra command \fB@IMAGEX_PROGNAME@
-optimize\fR, which lets you easily remove wasted space in a WIM (which can arise
-after a WIM image is appended or mounted read-write).  It also makes it easy to
-recompress a WIM file at the highest compression level.
-.IP \[bu]
-\fB@IMAGEX_PROGNAME@\fR also offers the command \fB@IMAGEX_PROGNAME@ join\fR,
-which lets you easily join the parts of a split WIM.
-.IP \[bu]
-For convenience, \fB@IMAGEX_PROGNAME@\fR automatically preserves the integrity
-table in WIMs that have one, even when \fB--check\fR is not specified.
-.IP \[bu]
-wimlib supports a special "pipable" WIM format (not compatible with Microsoft's
-software).  This allows capturing and applying images directly to standard
-output or from standard input, respectively; this can be used to pipe images to
-or from a server over the network to implement fast filesystem imaging and
+Multi-platform support.  \fB@IMAGEX_PROGNAME@\fR is supported on both UNIX-like
+systems (mainly Linux, but also FreeBSD, Mac OS X, etc.) and Windows, and most
+code is shared among all platforms.  However, platform-specific features are
+supported when possible.
+.IP \[bu]
+On UNIX-like systems, integration with libntfs-3g allows capturing a WIM image
+directly from a block device containing an NTFS volume, or applying a WIM image
+directly to a block device containing an NTFS volume.  This allows saving and
+restoring NTFS-specific data, such as security descriptors and named data
+streams, which is otherwise only supported on Windows.  This feature is
+unavailable if wimlib was was configured using --without-ntfs-3g.
+.IP \[bu]
+Long path support on Windows.  \fB@IMAGEX_PROGNAME@\fR can capture and apply
+files with paths exceeding the MAX_PATH (260 character) limitation of the Win32
+subsystem.
+.IP \[bu]
+Non-Administrator support on Windows.  You can run \fB@IMAGEX_PROGNAME@\fR
+without Administrator rights, subject to some limitations.
+.IP \[bu]
+Support for WIM integrity tables.  An integrity table is a list of SHA-1 message
+digests appended to the end of a WIM file which gives checksums over the WIM
+file itself.  The \fB--check\fR option to several \fB@IMAGEX_PROGNAME@\fR
+commands can be used to verify or add integrity tables.
+.IP \[bu]
+Support for "pipable" WIMs.  This is a wimlib extension and is not compatible
+with the Microsoft implementation.  A pipable WIM, created with
+\fB@IMAGEX_PROGNAME@ capture\fR with the \fB--pipable\fR option, can be written
+to standard output or read from standard input.  This can be used to pipe images
+to or from a server over the network to implement fast filesystem imaging and
 restore.
 .IP \[bu]
-\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.)
+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 later v1.6 releases 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 a 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.
 .SH LOCALES AND CHARACTER ENCODINGS
-WIM files themselves store file and stream names using UTF-16LE.  On Windows,
-wimlib works in UTF-16LE, so conversions are usually not necessary and there
-should be no problems with character encodings.
+WIM files themselves store file and stream names using Windows native "wide
+character strings", which are UTF-16.  On Windows, wimlib works using these same
+strings, so conversions are usually not necessary and there should be no
+problems with character encodings.
 .PP
 On UNIX-like systems, wimlib works primarily in the locale-dependent multibyte
 encoding, which you are strongly recommended to set to UTF-8 to avoid any
 problems.  You can alternatively set the environmental variable
 \fBWIMLIB_IMAGEX_USE_UTF8\fR to force \fB@IMAGEX_PROGNAME@\fR to use UTF-8
-character encoding internally, even if the current locale is not UTF-8
-compatible.
+internally, even if the current locale is not UTF-8 compatible.
 .SH CASE SENSITIVITY
 By default, the case sensitivity of \fB@IMAGEX_PROGNAME@\fR differs somewhat
 between UNIX-like systems and Windows.  WIM images may (but usually do not) have
@@ -189,25 +212,27 @@ actually provided by the user for use in a WIM image (e.g. for extracting,
 adding, renaming, or deleting files) will by default be treated as
 case-insensitive in order to get the "expected" behavior. This differs from the
 default behavior on UNIX-like systems, where such paths will be treated as
-case-sensitive.  Note that with case insensitivity, a path component may in
-general be ambiguous due to multiple files or directories having the same
-case-insensitive name.  In such cases, if there is a file or directory with an
-exactly matching name, it is chosen; otherwise, one of the case-insensitively
-matching file or directories is chosen arbitrarily.
+case-sensitive.
+.PP
+Note that with case insensitivity, a path component may in general be ambiguous
+due to multiple files or directories having the same case-insensitive name.  In
+such cases, if there is a file or directory with an exactly matching name, it is
+chosen; otherwise, one of the case-insensitively matching file or directories is
+chosen arbitrarily.
 .PP
-The default behavior can be overridden by explicitly setting the environmental
-variable \fBWIMLIB_IMAGEX_IGNORE_CASE\fR to 1, in which case such paths will be
-treated case insensitively, or 0, in which such paths will be treated case
-sensitively.
+The default case sensitivity of \fB@IMAGEX_PROGNAME@\fR can be overridden by
+explicitly setting the environmental variable \fBWIMLIB_IMAGEX_IGNORE_CASE\fR to
+1, in which case such paths will be treated case insensitively, or 0, in which
+such paths will be treated case sensitively.
 .PP
 Regardless of these settings, options and non-path arguments must be specified
 in lower case.
 .SH LICENSE
-wimlib and \fB@IMAGEX_PROGNAME@\fR are distributed under the GNU General Public
+wimlib and @IMAGEX_PROGNAME@ are distributed under the GNU General Public
 License version 3 or later.  Be aware this means this software is provided as-is
 and has no warranty; see COPYING for details.
 .SH REPORTING BUGS
-Report bugs to ebiggers3@gmail.com.
+Report bugs to ebiggers3@gmail.com.  Feedback and suggestions are also welcome.
 .SH SEE ALSO
 .BR @IMAGEX_PROGNAME@-append (1),
 .BR @IMAGEX_PROGNAME@-apply (1),