X-Git-Url: https://wimlib.net/git/?p=wimlib;a=blobdiff_plain;f=doc%2Fman1%2Fwimlib-imagex-apply.1;h=0fad8dd41fbda7a1aad0e210272391e58fe6bc55;hp=1680a9448465c0824ef44086619e63e5bc115339;hb=5260cf0b5649fc25b9d69a97f9604a3be257e13e;hpb=b4d8b14450c1f36ad07706888d9042bce5d9c2e0

diff --git a/doc/man1/wimlib-imagex-apply.1 b/doc/man1/wimlib-imagex-apply.1
index 1680a944..0fad8dd4 100644
--- a/doc/man1/wimlib-imagex-apply.1
+++ b/doc/man1/wimlib-imagex-apply.1
@@ -1,4 +1,4 @@
-.TH WIMLIB-IMAGEX "1" "January 2016" "wimlib 1.9.0" "User Commands"
+.TH WIMLIB-IMAGEX "1" "March 2016" "wimlib 1.9.1" "User Commands"
 .SH NAME
 wimlib-imagex-apply \- Extract one image, or all images, from a WIM archive
 .SH SYNOPSIS
@@ -126,10 +126,7 @@ mode:
 .IP \[bu] 4
 Encrypted files will not be extracted.
 .IP \[bu]
-wimlib v1.7.0 and later:  Sparse file attributes will not be extracted (same
-behavior as ImageX/DISM/WIMGAPI).  wimlib v1.6.2 and earlier:  Although sparse
-file attributes will be applied, the full data will be extracted to each sparse
-file, so extracted "sparse" files may not actually contain any sparse regions.
+Sparse file attributes will not be extracted.
 .PP
 Regardless, since almost all information from the WIM image is restored in this
 mode, it is possible (and fully supported) to restore an image of an actual
@@ -177,8 +174,8 @@ descriptors for individual files or directories may be omitted or only partially
 set if the user does not have permission to set them, which can be a problem if
 \fBwimlib-imagex\fR is run as a non-Administrator.
 .IP \[bu]
-File attributes, including hidden, sparse, compressed, encrypted, etc, when
-supported by the filesystem.
+File attributes, including hidden, compressed, encrypted, etc, when supported by
+the filesystem.
 .IP \[bu]
 DOS names (8.3) names of files; however, the failure to set them is not
 considered an error condition.
@@ -193,6 +190,8 @@ Additional notes about extracting files on Windows:
 exact metadata and data of the WIM image, for example due to features mentioned
 above not being supported by the target filesystem.
 .IP \[bu]
+Sparse file attributes will not be extracted.
+.IP \[bu]
 Since encrypted files (with FILE_ATTRIBUTE_ENCRYPTED) are not stored in
 plaintext in the WIM image, \fBwimlib-imagex\fR cannot restore encrypted
 files to filesystems not supporting encryption.  Therefore, on such filesystems,
@@ -366,9 +365,8 @@ target volume is NTFS or another filesystem that supports reparse points.
 .IP ""
 In addition, this option works best when running on Windows 8.1 Update 1 or
 later, since that is the first version of Windows that contains the Windows
-Overlay File System Filter Driver ("WOF").  If the WOF driver is detected,
-wimlib will create the WIMBoot "pointer files" using documented ioctls provided
-by WOF.
+Overlay Filesystem filter driver ("WOF").  If the WOF driver is detected, wimlib
+will create the WIMBoot "pointer files" using documented ioctls provided by WOF.
 .IP ""
 Otherwise, if the WOF driver is not detected, wimlib will create the reparse
 points and edit the file "\\System Volume Information\\WimOverlay.dat" on the
@@ -457,7 +455,7 @@ wimlib-imagex apply install.wim 1 /dev/sda2
 .PP
 Note that before running either of the above commands, an NTFS filesystem may
 need to be created on the partition, for example with format.exe on Windows or
-\fBmkntfs\fR(8) (part of NTFS-3g) on UNIX-like systems.  For example, you might
+\fBmkntfs\fR(8) (part of NTFS-3G) on UNIX-like systems.  For example, you might
 run:
 .RS
 .PP