X-Git-Url: https://wimlib.net/git/?p=wimlib;a=blobdiff_plain;f=doc%2Fimagex-apply.1.in;h=591142714f154a421ffce0185aecd2a94c6bbf63;hp=d60c53d64acbc6386c92b1fca3e2b9e61086b81b;hb=7acdc3aecd7ce546727ae8239e0d942c2a00db43;hpb=a381a9e10a60c7790fe33255c949bf55b5872a8d

diff --git a/doc/imagex-apply.1.in b/doc/imagex-apply.1.in
index d60c53d6..59114271 100644
--- a/doc/imagex-apply.1.in
+++ b/doc/imagex-apply.1.in
@@ -48,7 +48,8 @@ The default (unnamed) data stream of each file
 Hard links
 .IP \[bu]
 File and directory creation, access, and modification timestamps to the nearest
-microsecond, if supported by the underlying filesystem
+100 nanoseconds, if supported by the underlying filesystem, operating system,
+and C library
 .IP \[bu]
 Symbolic links and junction points, although they will not necessarily point to
 the desired location (for example, the target of the link may contain a Windows
@@ -197,23 +198,24 @@ imagex apply mywim.swm 1 dir --ref="mywim*.swm"
 
 This section documents the differences between \fBimagex apply\fR in the Windows
 builds of wimlib versus the rest of this man page, which is written to document
-UNIX version.
+the UNIX build.
 
 \fBimagex apply\fR does not have separate "normal" and "NTFS" modes on Windows.
 There is simply one mode, and it uses the Windows API to apply NTFS-specific
 information, including alternate data streams, reparse points, hard links, and
 file attributes.  So, you essentially get the advantages of the "NTFS mode"
 documented above, but you can apply the WIM image to any directory, not just an
-entire NTFS volume.  This is mostly the same behavior as Microsoft's ImageX.
+entire NTFS volume.  This is essentially the same behavior as Microsoft's
+ImageX.
 
 \fB--hardlink\fR, \fB--symlink\fR, and \fB--unix-data\fR are not supported on
 Windows.
 
-Other than the differences documented in this section, the Windows version
-should be essentially equivalent to the UNIX version.  However, one additional
-thing to note is that wimlib's Windows version of ImageX is NOT written to be
-command-line compatible with Microsoft's version of ImageX, although they are
-very similar.
+Except for the differences documented in this section, the Windows build of
+\fBimagex apply\fR should be essentially equivalent to the UNIX build.  However,
+one additional thing to note is that wimlib's Windows ImageX is NOT written to
+be command-line compatible with Microsoft's ImageX, although they are very
+similar.
 
 .SH OPTIONS
 .TP 6
@@ -257,9 +259,9 @@ the WIM file.  It is an error if the message digests don't match.  It's also
 considered to be an error if any WIM resources cannot be found in the stream
 lookup table.  So you can be fairly certain that the file streams are extracted
 correctly, even though \fBimagex apply\fR don't have a \fB/verify\fR option like
-Microsoft's version of imagex does.  Please note that this is separate from the
-integrity table of the WIM, which provides SHA1 message digests over raw chunks
-of the entire WIM file and is checked separately if the \fB--check\fR option is
+Microsoft's ImageX does.  Please note that this is separate from the integrity
+table of the WIM, which provides SHA1 message digests over raw chunks of the
+entire WIM file and is checked separately if the \fB--check\fR option is
 specified.
 
 You cannot use \fBimagex apply\fR to apply a WIM from a pipe (such as standard